paul at linuxaudiosystems.com
Mon Oct 25 19:30:30 PDT 2004
>> And sometimes my keyboard short-cuts seem to stop functioning.
>I see this a lot with beta19. It's frustrating. Usually, the
>keyboard starts working again if I shift to a different workspace and
we know why this happens. its related to handling of crossings in and
out of what X calls "inferior" windows. we changed the code there to
handle another related bug, but it seems to have triggered a worse
one. i have read all i can about how this is supposed to work, but i
still don't understand it. the central problem is that we have
different keyboard bindings in the editor and mixer windows, and we
also have to other window/keyboard interactions. its a very
complicated mess, much more than in apps with a consistent set of
bindings and/or just one window plus some popups.
>Also, if I create a new track and then type in its name, the keyboard
>focus remains there for the rest of the session. If I use the
>spacebar to start or stop playback, I get an extra space in the name,
>instead. How do I redirect the keyboard after typing a name?
its the same issue. when we fix one, we will fix the other.
>> One more thing, it is great being able to move the play-head by just
>> grabbing it with the cursor, but maybe the "grab"area around the
>> playhead cursor could be increased.
>Being particulary klutzy with the mouse, I need this too. It always
>takes me two or three tries to grab the play-head successfully.
this is a general GNOME::Canvas issue. there is a "close-to" distance
that the entire canvas uses to define whether the cursor hotspot is
"within" an object. you can't change it on a per-object basis.
More information about the Ardour-Dev