[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LSR search not working?
From: |
Thomas Morley |
Subject: |
Re: LSR search not working? |
Date: |
Sun, 7 Feb 2016 23:31:06 +0100 |
2016-02-07 12:13 GMT+01:00 Pierre Perol-Schneider
<address@hidden>:
> 2016-02-05 10:38 GMT+01:00 Thomas Morley <address@hidden>:
>> - Doc-tag is removed. The way the bass-signs, "///a" etc, are done
>> feels more like a workaround.
>> Not sure about it, though. Phil cc-ed, a second opinion would be nice.
>
>
> This is definitely a workaround. Thing is, there is no reason that I know to
> put each bass lute string as single, or?
I wonder if it would be possible to tweak TabStaff to put out "///a",
etc for pitches below lowest string.
I mean, TabStaff is a special Staff. A common Staff uses LedgerLines
for lower pitches...
Worth some research/test I'd say.
No clue when I'll have the time for it, though...
Cheers,
Harm
- LSR search not working?, Nick Payne, 2016/02/04
- Re: LSR search not working?, Pierre Perol-Schneider, 2016/02/04
- Re: LSR search not working?, Thomas Morley, 2016/02/04
- Re: LSR search not working?, Pierre Perol-Schneider, 2016/02/04
- Re: LSR search not working?, Pierre Perol-Schneider, 2016/02/05
- Re: LSR search not working?, Thomas Morley, 2016/02/05
- Re: LSR search not working?, Pierre Perol-Schneider, 2016/02/07
- Re: LSR search not working?,
Thomas Morley <=
- Re: LSR search not working?, Pierre Perol-Schneider, 2016/02/08
- Re: LSR search not working?, Thomas Morley, 2016/02/09
- Re: LSR search not working?, Pierre Perol-Schneider, 2016/02/09