From: Ray K. <ray...@yw...> - 2004-10-11 13:53:37
|
Heres a thing I still would like changed in V1.0 When you mouse-up after dragging a note, that note is still selected, so if= =20 you want to drag another note, you have to click on the background to=20 unselect it before dragging the next note. Otherwise the first note (which= =20 was presumably in the right place) gets dragged along with second note. I=20 would rather the notes deselected themselves immediately on mouse-up after = a=20 drag operation. thx |
From: Guillaume L. <gla...@te...> - 2004-10-11 14:57:19
|
Ray Klassen wrote: > > I > would rather the notes deselected themselves immediately on mouse-up after a > drag operation. That's not really consistent with usual drag'n drop behavior, is it ? -- Guillaume http://telegraph-road.org |
From: Steve C. <ste...@li...> - 2004-10-11 17:44:05
|
> That's not really consistent with usual drag'n drop behavior, is it ? Not as previously described. I have, however, noticed that quite often when selecting a note that I end up getting both the desired note and the previously selected one(s) inadvertantly unless I first deselect the previous notes. This can be a little pesky if say, I'm moving the new note up or down a semitone and the previsouly selected notes come along for the ride. Especially when these hitchhiker notes are out of sight somewhere beyond the edge of the window and the problem doesn't manifest itself until playback. Perhaps the original description could have been worded better. |
From: Chris C. <ca...@al...> - 2004-10-11 17:46:03
|
On Monday 11 Oct 2004 15:06, Guillaume Laurent wrote: > Ray Klassen wrote: > > I would rather the notes deselected themselves immediately on > > mouse-up after a drag operation. > > That's not really consistent with usual drag'n drop behavior, is it? Sounds to me like the proper fix would be that if you click to drag an event that is not already selected then that event should become the sole selection and anything else currently selected should become unselected. I'm not sure how many people are relying on the current behaviour, but I bet it's fewer than are being caught out by stuff being moved apparently at random because they happened to have a selection somewhere else before they started dragging. I'm sure I had a reason for doing it the way it is, but it seems to me now that it was probably a stupid one. What do you think? Chris |
From: Chris C. <ca...@al...> - 2004-10-11 18:23:18
|
On Monday 11 Oct 2004 18:56, Chris Cannam wrote: > Sounds to me like the proper fix would be that if you click to drag > an event that is not already selected then that event should become > the sole selection and anything else currently selected should > become unselected. I take Steve Conrad's earlier email to be in agreement with this. I've filed a bug report and implemented the fix as described above, now in CVS. https://sourceforge.net/tracker/index.php?func=detail&aid=1044754&group_id=4932&atid=104932 Other comments or opposition still welcome. Chris |
From: Steve C. <ste...@li...> - 2004-10-11 18:50:27
|
> I take Steve Conrad's earlier email to be in agreement with this. You take it correctly. The current behaviour is more what I'd expect if the control key were being held down while clicking. |
From: Silvan <dmm...@us...> - 2004-10-15 21:14:25
|
On Monday 11 October 2004 02:34 pm, Chris Cannam wrote: > On Monday 11 Oct 2004 18:56, Chris Cannam wrote: > > Sounds to me like the proper fix would be that if you click to drag > > an event that is not already selected then that event should become > > the sole selection and anything else currently selected should > > become unselected. > Other comments or opposition still welcome. No, that sounds just right to me. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Guillaume L. <gla...@te...> - 2004-10-11 18:19:26
|
On Monday 11 October 2004 19:56, Chris Cannam wrote: > > Sounds to me like the proper fix would be that if you click to drag an > event that is not already selected then that event should become the > sole selection and anything else currently selected should become > unselected. Wow, yeah, I just tried and Ray is absolutely right (now that I understand what he meant) : the previously selected note remains selected when you click on another one, it is unselected only when you release the mouse button. So a press-drag-release does have the described effect, and it's definitely broken. Bad Chris, bad. -- Guillaume. http://www.telegraph-road.org |
From: Silvan <dmm...@us...> - 2004-10-12 01:39:13
|
On Monday 11 October 2004 02:19 pm, Guillaume Laurent wrote: > On Monday 11 October 2004 19:56, Chris Cannam wrote: > > Sounds to me like the proper fix would be that if you click to drag an > > event that is not already selected then that event should become the > > sole selection and anything else currently selected should become > > unselected. > > Wow, yeah, I just tried and Ray is absolutely right (now that I understand > what he meant) : the previously selected note remains selected when you > click on another one, it is unselected only when you release the mouse > button. So a press-drag-release does have the described effect, and it's > definitely broken. Bad Chris, bad. Broken, but also documented in my book already. Should I cut this out then? "TIP: I find that I have a tendency to surprise myself with this feature. It is not necessary to select an element before dragging it, and neither is it a requirement that you only move a note from your selection. If you have a selection off to the side somewhere, it is very easy to forget that it is going to move too. When you perform the actual drag operation, there is no visual indication that the selected notes are going along for the ride. If the selection is not visible, you might not even notice what has happened until some time after performing the drag. This is not a bug, but it often feels like one. I have stubbed my toe on this innumerable times." -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Guillaume L. <gla...@te...> - 2004-10-12 05:38:07
|
On Tuesday 12 October 2004 03:39, Silvan wrote: > > Broken, but also documented in my book already. Should I cut this out > then? > > "TIP: I find that I have a tendency to surprise myself with this feature. > [...] Yes. -- Guillaume. http://www.telegraph-road.org |