Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 2064 - Linux: ESC key does not work to abort drags in the Timeline Ruler
Linux: ESC key does not work to abort drags in the Timeline Ruler
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: User Interface
2.3.1
Per OS Linux
: P4 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-10 08:19 UTC by Peter Sampson
Modified: 2019-04-05 08:50 UTC (History)
6 users (show)

See Also:
Steps To Reproduce:
1) drag a section in the Timeline rule as a precursor to TQP 2) use the ESC key to abort the Timeline selection 3) doesn't work 4) pin the play head 5) play some sound 6) drag the pinned play head 7) use the ESC key to abort dragging 8) doesn't work
Release Note:
On Linux the ESC key does not work to abort drags in the Timeline Ruler on Linux. That includes play region boundaries and the pinned playhead.
First Git SHA:
Group: ---
Workaround:
None
Closed: 2019-04-05 00:00:00
petersampsonaudacity: Test‑OK‑Win+
petersampsonaudacity: Test‑OK‑Mac+
stevethefiddle: Test‑OK‑Lin+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Sampson 2019-02-10 08:19:04 UTC
ESC key won't work to abort drags in the time Ruler on Linux.  That includes play region boundaries and the pinned play head.

This is a residual as a result of the fix (on Linux) for Bug #2056
Comment 1 Peter Sampson 2019-02-10 10:48:02 UTC
Reduced to P4 following discussion with Steve
Comment 2 Steve Daulton 2019-02-10 11:23:23 UTC
I misunderstood what this bug was until I tried it, but now that I've tried and tested it, what's wrong with just pressing Spacebar to stop Quick Play, or am I missing something?

With regard to dragging a pinned play head, why do I need to be able to escape from a drag (requiring use of my other hand) when I can simply drag it back with the mouse, that is already dragging the play head?
Comment 3 Paul L 2019-02-10 11:25:46 UTC
I have already worked out a fix for this in a branch in my fork:

https://github.com/audacity/audacity/commit/07e50b60eebcc174cf464c67baa487d49deb934f

I also updated steps to reproduce to include drags of the pin.
Comment 4 Paul L 2019-02-10 11:30:36 UTC
(In reply to Steve Daulton from comment #2)

I wish to have a uniform convention in the user interface, that any mouse drag can be escaped with the key.  If a user knows this convention, which other applications follow too, then it relieves them of the annoyances of unintended drags of the wrong thing and makes it easy to restore things to their exact state before the drag.  I did much work to make this so for TrackPanel and for dragging of toolbars.  I want it so for the drags in the time ruler too.
Comment 5 Paul L 2019-02-10 11:30:59 UTC
Not yet "Fix made" while this commit is not in master.
Comment 6 Steve Daulton 2019-02-10 11:35:58 UTC
(In reply to Paul L from comment #4)
> If a user knows this convention, which other applications follow too...

"Some" other applications follow this convention, but it far from universal. For example, in Firefox, if I scroll the window using the vertical scroll bar, the Esc key does nothing.

While conventions are useful for maintaining consistent behaviour, we don't have to be obsessive about them in cases where they offer little or no added value.
Comment 7 Paul L 2019-02-10 11:44:04 UTC
(In reply to Steve Daulton from comment #6)

That sounds like an argument to treat the fix as low priority, as indeed it was assigned, but not an argument against attempting it at all.

There was also my desire to unify commonalities in mouse event handling of TrackPanel and AdornedRulerPanel in one common base class -- which make that big complicated AdornedRulerPanel::OnMouseEvents function go way in favor of classes derived from UIHandle.  Having done that, ESC key handling becomes an easy extra part of the bargain.
Comment 8 Steve Daulton 2019-02-10 11:47:43 UTC
(In reply to Paul L from comment #7)
Yes, I think it's a low priority bug, but it is a bug non the less, as it is not the behaviour that you intended.
Comment 10 Steve Daulton 2019-04-05 08:01:10 UTC
Works for me. Resolved Fixed.