Bugzilla – Bug 1396
In TQP we have lost the selection guide-line on the waveform
Last modified: 2018-08-20 11:51:45 UTC
When hovering in the Timeline (with Quick-Play enabled) In 2.1.1 and 2.1.2 in addition to the hand pointer in the Timeline there was also a small green playhead and a corresponding line on the waveform to indicate the potential TQP position. This is a yellow line, but I note the manual says it is a white line and shows it as such http://alphamanual.audacityteam.org/man/Timeline#tqp . Testing on the latest aplhas for W10 and Mac El Capitan shows that the small green playhead and the yellow/white line are no longer shown. Furthermore, if you click in the Timeline to invoke Quick-Play and leave the mouse cursor over the Timelinene then as Play commences a small green playhead and a yellow/white line are displayed at the start point of the Quick-Play. As you move the mouse poiinter within the Timeline that playhead and line do not move bit stay fixed - then if you move your mouse pointer out of the Timeline the small green playhead and the yellow/white line disappear. Marked as a regression - the yellow/white line is very useful in positioning the accurate start of a Quick-Play
(In reply to Peter Sampson from comment #0) Peter wrote: > ...and a corresponding line on the waveform to indicate the potential >TQP position. This is a yellow line, but I note the manual says it is >a white line and shows it as such Ahhh mote careful reading of the Manual tells me that it is yellow when Snap To is on and white when it's off.
Tests ok on W10 audacity-win-rad711e7-2.1.3-alpha-23-jun-16 and on Mac El Capitan d6187f6 21Jun16 This appears to be working properly now with the white/yellow selection guide-lines showing. It is not document as devel-fixmade here, but I think this was probably fixed by Paul as part of his scrubbing activities. Steve informed me by email that this was working on the latest Linux build now (which was what prompted this test).
Paul noted the loss of the white/yellow line in http://bugzilla.audacityteam.org/show_bug.cgi?id=1395#c4 and the fix was discussed and made there.
