On Monday 14 September 2009, Julie S wrote: > The purple cursor is gone so you say, but it doesn't have to reappear as > old code had it, we can just use it "metaphorically" and overlay it or > something like it on the dark cursor. It's sole purpose it to mark the > active staff.
Well, taking the "get this done today" approach, the cursor already marks the active staff in the scheme we have today. The cursor jerks along to whatever the staff it's following contains, but we don't have cursors on different staffs in the same notation view moving at different speeds, or anything crazy like that. The biggest beef is if you have two staffs one above the other, and you're parked on the whole note staff, it will follow the whole notes, and appear not to be moving for big stretches of time, even though the staff right below has a bunch of 8th notes. This is even worse if the two segments overlap, and you're following the whole notes even though there are also a bunch of 8th notes on this same staff. What you were saying about the cursor this and the cursor that are ideas that I'd love to talk about if someone else was about to sit down and code it all, but I have the impression I'm pretty well on my own on this one. I'm inclined to do the least work possible from here, and that means trying to live with the snapping cursor if at all possible. (And if not, a sweep cursor that continues to be bound to the single active staff and the active segment on it, and snaps back to a logical place when playback stops.) I think the obnoxiousness of its behavior would be greatly mitigated by a convenient and accessible way to roll through which bit of what is active and being tracked. I think the mechanism I have in mind to try for that would probably be nice regardless of whether the cursor snaps or not, so I have in mind to try this approach first, and ignore how much I dislike the snapping cursor. (For one thing, I really despised it initially, but I've largely gotten used to it.) I don't know exactly where I'll put it and so on, but my plan of attack is: 1) Get the four navigation options to move up/down staff and next/prev segment to work via keyboard shortcuts that call functioning code 2) Stack two vertical thumb wheels on top of each other, one to roll through the active staff, and one to roll through which segment on which staff is "on top" (probably on a floatable vertical navigation toolbar) I think with the thumb wheels (from Sonic Visualiser. They're quite nice widgets) making it possible to roll through the permutations very quickly and accessibly, it would probably not be too confusing having the cursor behave as it currently does. If it's still a great bother, we would have wanted the thumb wheels anyway, so nothing is wasted. I really do want some nice way to navigate through all of this stuff, which in Classic always depended on keyboard shortcuts I could never remember properly. A horizontal toolbar would fit in better with the overall layout, but I feel vertical controls would be much more intuitive to use. Maybe I could just manage to stick them under the groups toolbar. > Overlapping segments and other related thoughts: I'm just glossing over this for now, having digested your brainstorms. We may have time to return to this question before Thorn, but probably won't. -- D. Michael McIntyre ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
