Paul Licameli
2017-06-29 17:52:12 UTC
This was occasion for argument over wording of a status message, when it
seems more is needed.
How seriously do we want to do something about this old "bugbear"?
If you try to click and drag starting at a boundary between clips, meaning
to select, you merge the clips which is not what you really want.
(Of some relevance is my recent commit
1c0af829030e4f0a294a15724167be88f46d6b56. This makes this click to join
unavailable in spectrogram view, because the boundaries are not drawn.)
I throw out some proposals, disregarding development difficulty for now.
1. Don't join the clip until button-up. If a drag begins before that,
select instead.
2. Implement TAB key cycling among hit-test candidates. (Just that, not
going the whole distance, of abolishing the Tools toolbar.)
3. Restrict click-to-join to only a part (which?) of the vertical extent
of the line. Make some cursor distinction from selection.
4. As (3) but with more display changes for discoverability:
1. Draw something like an X in a box or circle, as the restricted hit
target, and draw it always in non-spectrogram views.
2. As (1) but drawn only when the pointer is over the line, but then,
over any part of it.
The question also arises, what to do for cutlines. If we do version 3 for
boundaries, then similar ought to be done for cutlines, but then perhaps we
need to draw two thingies, one to delete, and another (like the east-west
cursor?) to expand.
PRL
seems more is needed.
How seriously do we want to do something about this old "bugbear"?
If you try to click and drag starting at a boundary between clips, meaning
to select, you merge the clips which is not what you really want.
(Of some relevance is my recent commit
1c0af829030e4f0a294a15724167be88f46d6b56. This makes this click to join
unavailable in spectrogram view, because the boundaries are not drawn.)
I throw out some proposals, disregarding development difficulty for now.
1. Don't join the clip until button-up. If a drag begins before that,
select instead.
2. Implement TAB key cycling among hit-test candidates. (Just that, not
going the whole distance, of abolishing the Tools toolbar.)
3. Restrict click-to-join to only a part (which?) of the vertical extent
of the line. Make some cursor distinction from selection.
4. As (3) but with more display changes for discoverability:
1. Draw something like an X in a box or circle, as the restricted hit
target, and draw it always in non-spectrogram views.
2. As (1) but drawn only when the pointer is over the line, but then,
over any part of it.
The question also arises, what to do for cutlines. If we do version 3 for
boundaries, then similar ought to be done for cutlines, but then perhaps we
need to draw two thingies, one to delete, and another (like the east-west
cursor?) to expand.
PRL