UPDATE: I have discovered 2 things:
1) If the action "pad-note-64" is removed from the function MuseScore::enableInputToolBar() (file mscore/musescore.cpp, line 4149), QAction::eventFilter no longer reports an "Ambiguous shortcut overload" and both actions can be used in their respective contexts ([1] to enter a fret mark "1" in TAB entry mode and to select 1/64 duration in other modes). 2) Once the 'normal' "pad-note-..." actions are restricted out of TAB entry mode, their toolbar buttons cannot be used any longer in that mode (which make sense, after all). This seems to imply that actions linked to toolbar buttons cannot have context-dependent usage and that the solution described in http://musescore.org/en/node/20357 <http://musescore.org/en/node/20357> cannot be implemented. Any further help, suggestion, comment is welcome. Thanks, Maurizio -- View this message in context: http://dev-list.musescore.org/Help-with-shorcuts-tp7577975p7577977.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
