Hi Tim, 01.11.2015 12:00, Tim E. Real wrote: > On November 1, 2015 11:17:43 AM Andrew Deryabin wrote: >> Hi Tim, > Hey! 3 AM Still awake here.
git, git, git :) > >> Just updated! >> >> It's like a time machine - to the future with one click! >> >> Persistent routes work - my midi keyboard now connects automatically - >> it's very very useful thing :) >> >> Now I want to post some comments about new router. >> >> 1. I suggest not to close individual routes submenu (with red >> checkboxes) after clicking, because, for example, to connect 2 channels >> one have to open this submenu twice. Can you make it stay on top until >> it looses focus (pressing 'jack' channel button or clicking somewhere >> outside routes popup menu)? With this behavior we can select all needed >> channels after just one menu opening. And I think it will be simply more >> useful and clearer. > Er... Holding Ctrl while clicking has always kept the popups open. > And they can be told to stay open without Ctrl, via an item in Settings Menu. > > So are you asking that even in the case where Ctrl would normally need to > be held here for these types of tracks, that we instead force it to stay > open > no matter what? Yes, I think it will be the right fix. As for me, I like to play something on midi keyboard with left hand and clicking mouse with right. So I can't press ctrl at this time. What about changeable item in settings - it's ok for other types of popups, but route popup should stay opened no matter what state of ctrl or setting is. > >> 2. When not selecting omni checkbox but using individual route channels >> it would be nice to make gray checkbox in 'omni' column indicating that >> there are some individual channels selected, because now we must open >> every route submenu to know where signal goes (if 'omni' mode is disabled). > Ha! Yeah an indication of some kind... > I tried to think of a way to show everything at once in either the top menu > or at least each submenu. Maybe I should try again. Thanks! > > Catch you tomorrow. > Thanks. > Tim. > >> All for now. Checking further :) >> >> 01.11.2015 08:09, Tim E. Real пишет: >>> Hey hey! >>> See the ChangeLog for details. >>> >>> Man, that merge was... >>> >>> scary ;-) >>> >>> After the top directory was renamed muse3, my whole KDevelop >>> >>> project went blank when I pulled :-( >>> >>> I eventually got going simply by 'opening' a new KDevelop project based >>> >>> on the new pull. >>> >>> And there was one conflict to be resolved, which muddied the water. >>> >>> My commit message erroneously says "merge from master" when it >>> >>> should say "merge from new_router", because I was confused >>> when merging back to master, GitCola committed for me with the >>> old message from when I pulled from master. >>> >>> I hope the concepts presented are good. I worry if I implemented them >>> well. >>> Much trepidation... >>> >>> Routing dialog is in progress, graphic fixes, more integration with popups >>> etc. Other stuff still in progress too. Maybe a few bugs in there. >>> Two files still 'dirty' while work in progress: node.cpp and >>> routedialog.cpp >>> >>> >>> Robert: >>> ------------ >>> You added the file loading progress dialog, long ago. >>> I had to change it to non-modal so that my 'file version warning dialog' >>> >>> could be shown in front of it and take priority. >>> >>> My warning dialog runs from deep within the file loading code which is >>> >>> 'bracketed' by the progress dialog. >>> >>> Hopefully I can revert your dialog to modal and instead pass a flag up >>> >>> the calling chain so my warnings can be shown AFTER the progress >>> dialog closes. >>> >>> Andrew: >>> ----------- >>> I tweaked the PopupMenu code a wee bit, trying to expand the >>> >>> scrolling abilities. The scroll can stay open now. >>> >>> I found, maybe like you, that a menu won't scroll if it has children. >>> I guess that's why you named the feature scrollable /sub/ menus ;-) >>> >>> Also, I tweaked each of the synth classes' process methods a wee bit, >>> >>> including LV2, simply to change the 'input routes processing section' >>> near the beginning, to support the new Omni and Channel routing. >>> >>> Thanks. >>> Tim. >>> > > ------------------------------------------------------------------------------ > _______________________________________________ > Lmuse-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lmuse-developer -- Regards, Andrew ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
