On Saturday 12 September 2009, [email protected] wrote: > * Ctrl-key constrains movement to horizontal or vertical dependant on > movement - A compromise that leaves the SHIFT key clear for adding to > selections - Try it and let me know what you think
That's an interesting way to do it. It feels pretty good to me as far as me being able to tell it which way I want to constrain the drag through my actions. Using Shift to add or remove from selections also works nicely. > * If part of a selection hits the limits during a drag, the relative > positions of items are recovered when dragged back away again This is an interesting change on the vertical axis. One thing you can't do now is quickly level off a string of data points by shoving them against the stop at the top of bottom to flatten the line out, and then moving it back away from the stop. Now this involves letting go of the line to it stays fixed at, say, all 0, and then moving it from there in a two-step operation. This is probably better behavior overall, because hitting the stop doesn't clobber the value easily, but you can use the stops to move values if you really want to do so. On the horizontal axis, it all seems a bit more dubious. Data points won't go past the segment boundaries, and if you pull back away from the wall, their previous relationship is maintained, but if you shove them to the wall and leave them there, it's eminently possible to wind up with a big stack of different values at exactly the same time. This is a pretty meaningless situation from a MIDI controller perspective, and it might be cleaner to just clip at these boundaries, and throw away any data points that get released on the wrong side. I think clipping would probably be better, but this whole observation is a quibble mixed with some thoughtful speculation, and not a demand at all. > * Drag auto scroll implemented for control ruler Works nicely! > * Mimic MatrixTool return of FollowMode in ControlTool classes Oh really, and did you do that with or without extra splorzleblats? (No idea what you're talking about on that one.) > * Added slotEnsureTimeVisible to MatrixWidget class > used to enable the above scroll OK. > * Quick value readout tryout > - currently shown for any selected item in the pitch bend ruler only This is simple enough and works for individual data points, but it has two big problems. First, if I know I'm trying to insert a value of 1492 for some reason, it's pretty much impossible to do this in one step unless I just randomly get lucky. First I have to click something into the big unlabeled blank empty space, and then I get to see what number I picked. Oh. 8157. No cigar. Then I can drag it to where I was trying to aim in the first place. Second, this works well for data points that have a wide horizontal separation, but it's extremely easy to glob a bunch of these value labels together into an indecipherable blue mess when they're closely spaced. For the first problem, I'm not exactly sure how it could be done, but it feels like I want some kind of follow-the-cursor thing that shows me a phantom data point representing what I will create if I click here. For the second problem, quite honestly, damn if I know Chris. That's a hard one. > * No scaling to (eg) difference from default yet > - would be better if displayed values were not raw midi values I don't have any spectacular ideas on this one. It would be nice to be able to display in whole tones, semitones, quarter tones, and even finer divisions, but I don't have the math close at hand for that, and I'm not quite sure how I'd want to see it work either. Sometimes you'd want ultra fine resolution, and sometimes it would be helpful if Rosegarden snapped to, say, semitones. I think all of that is probably a big "after Thorn" discussion about future possibilities, rather than anything we should realistically try to achieve at this juncture. In the interim, however, it seems like representing 8191 as 0 and showing the displayed values as if they were a signed int would be more intuitive, and consistent with how I vaguely half remember doing this in the past. Don't sequencers normally present "no pitch bend" as 0 and show + or - numbers from there? I think so, but can't prove it. I can't find anything off hand to play with. This would be worth a foray into Window Land if I had any copies of Windows around, or any Windows sequencers, but I don't on either score. Anyway all this picking it up and shaking it aside, this is all looking pretty damn plausible right now, Chris, and we could just about ignore all of these comments and release it in this condition if we were pushing closer against a deadline. Not to say I wouldn't like you to keep tweaking it, but I think the most critical make or break part of the whole thing is well behind us now. This is good stuff here. -- 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
