On Sunday 17 April 2016 09:46:40 D. Michael McIntyre wrote: > On 04/17/2016 07:29 AM, David Faure wrote: > > > When selecting multiple segments and editing them all together in the > > notation editor, > > Ctrl + Key_Left / Ctrl + Key_Right (which moves one bar at a time) stops at > > the boundaries > > of the current segment. Yet, the big blue marker in the main window keeps > > moving... > > > > NotationWidget::slotPointerPositionChanged() appears in the debug output, > > with increasing values > > even when the cursor is "blocked", so I'm not sure why the marker doesn't > > move in the notation editor. > > > > What's the intended behaviour? Should Ctrl + Key_Right keep going, into the > > next segment? > > That would be convenient, IMHO. > > The behavior with Left and Right to move one event at a time is to stop > at the end of the active segment. The cursor in the main window does > not move. As you point out, using the Ctrl+Left/Right version of this > does move the cursor in the main window. I hadn't ever noticed that, > and it's inconsistent. One or the other, surely, but never both > behaviors. This is an oversight.
Agreed. > I don't have a strong opinion on what to do when reaching the end of the > active segment. Stopping is fine with me. If I want to continue, I > change the active segment and do so. I am used to this, and can live > with it. Could Rosegarden save me a little effort and select the next > segment automatically? It certainly seems possible, and I don't have > any objection to giving that a try. It might work out splendidly. Yes, I don't see what the downside might be. > Trying to navigate with just the keyboard, I notice that it seems to be > impossible to change the active segment without reaching for the mouse. Exactly. > I have never been a keyboard navigation guy, and this does not bother > me, but I can see where it would bother a keyboard navigation guy. If > we can figure out some new keys to use for this, it seems like a good > idea to add some new shortcuts to call these slots via a different route. I don't understand why this would require an unintuitive new shortcut. What do we lose by letting Left/Right and Ctrl+Left/Right navigate to the next segment automatically? Or the other way around, what do we win by blocking navigation at the end of a segment? -- David Faure, [email protected], http://www.davidfaure.fr Working on KDE Frameworks 5 ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
