From: Florian J. <flo...@we...> - 2011-05-09 12:21:30
|
Am 08.05.2011 22:43, schrieb Tim E. Real: > On May 8, 2011 04:39:18 pm Robert Jonsson wrote: > >> 2011/5/6 Florian Jung<flo...@we...>: >> >>> Hi >>> >>> i'd like to remove the velocity- and gate-time-dialog's range-selection; >>> i'd like it to always operate on the current selection. >>> >> How about going halfway and preselecting "Selected events" if there >> are events selected? >> actually this looks like a good idea to me however, i can't stand dialogs which don't remember my settings... when i now click on "loop markers", i want the option to stay there over several dialog calls. has anyone any solution for this? >>> "all" is done by ctrl+a, then open that dialog >>> "loop markers" is done by<short cut must still be added>, then open it >>> >>> (pianoroll's "select" submenu has an action which selects everything in >>> the loop; adding a shortcut for it would rock ;) ) >>> >> I like shortcuts :) I'll take a look. >> >> thanks ;) >>> and "selection in loop"... who needs this xD? >>> > These are for manipulating stuff between the left and right blue marker lines. > Don't remove this stuff. It is useful, as there is no other way to specify a > 'range' of events. The combination of options provides the greatest > flexibility. One can have a whole whackload of events selected, yet simply by > manipulating the left/right markers, can narrow the effect of the operations. > i thought this could be solved by the above short cut selecting everything in the loop markers. and that flexibility... well, i don't think that it's needed. but anyway, we can simply let it in muse, a user who doesn't want to use it can simply ignore it ;) >>> this would greatly simplify things for me as developer, and i'd also >>> feel more familiar with "my" concept as user (you know, the cakewalk-guy >>> ;) ) >>> >>> what do you think about this? >>> >> Shortcuts are really the best for a power-user but I wonder if these >> dialogs would be harder to understand for beginners if the selection >> was not evident in the dialog? >> true :) >> How do you mean that it would simplify for you as a developer? You >> mean to implement this function in the score editor? >> i thought that i'll redo the selection system by really only allowing selections. no "notes in loop", "selection in loop" stuff etc, because i thought it is easier to implement. however, now, i have written functions which respect that "stuff", and it wasn't a big deal. i'd vote for: * add these short cuts * let that range-selection stuff. maybe make it collapsable in the dialogs for those who don't like it consider that topic as closed, as my main reason is away ;) flo |