From: Robert J. <spa...@gm...> - 2010-04-21 19:12:54
|
Hi Alex, a few weekends later... I just checked in code to enable Ctrl+Up/Down to move between tracks in the arranger, lemme know if it works. /Robert 2010/4/6 alex stone <com...@gm...>: > On Tue, Apr 6, 2010 at 1:44 AM, Robert Jonsson <spa...@gm...> wrote: >> Hi alex, >> >> I seldom use these shortcuts but I believe they are for moving between >> parts (Mathias invention and I know he uses it all the time) >> >> There was some work for moving selected track with the keyboard too >> but I believe it is disabled, not sure why (run out of shortcuts?!) >> I'll make a check later this week to see if it can be enabled. >> >> /Robert >> >> 2010/4/5 alex stone <com...@gm...>: >>> Going Up and Down to Next/Previous track. >>> >>> I can see bindings called Up and Down for moving from track to track, >>> but after trying up and down arrows, and the Page Up/Down keys, >>> nothing seems to happen. >>> >>> Are the Up/Down arrows intended to navigate tracks? If so, they don't >>> seem to work at the moment. >>> >>> Alex. >>> -- >>> www.openoctave.org >>> >>> mid...@op... >>> dev...@op... >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Lmuse-developer mailing list >>> Lmu...@li... >>> https://lists.sourceforge.net/lists/listinfo/lmuse-developer >>> >> > > Ok, thanks Robert. > > The actions i'm trying to find are moving track to track with > bindings. So each track in turn is highlighted, and with the feature > just built (moving record-arm with track) that means quickly > navigating a large score, without having to switch tracks with a > mouse. (blech) > > Alex. > -- > www.openoctave.org > > mid...@op... > dev...@op... > |