Thank you and 
sorry I didn't explain myself quite clearly.

Marc Sabatella wrote
>  my point is, ties are not unique in this, or even a
> particualrly good example, because ties are probably deleted *less* often
> than other elements in normal usage.  

You are right it's not about deleting ties. Although it would be helpful to
be able to toggle ties ON and OFF.


Marc Sabatella wrote
> As for the need to click something in order to delete it, that is indeed a
> limitation we hope to remove some day, by providing more keybaord
> navigation. 

Thats exactly what I mean. At some point a writer really wants to eliminate
any need for mouse clicks and extra key strokes as much as possible. 

Another thing that came to my mind...

You basically have three different editing "modes":
*note input*, *range selection*, and *single element selection *.
They all share some mutual functionality while certain things are only
available at one mode or another 
like:
- repeat command (R key) is only available at the note input and range
selection mode, but not if you've selected a single note
- you cannot make a  range selection while in the note input mode.
- you can not add a dot to the note in range selection or note input mode
directly.
- Del(backspace) key acts somewhat like a Ctrl Z command when in the note
input mode (instead of deleting the note entirely leaving a rest it brings
back the note that was entered before the correction was made).
To me it's a potentially excessive key striking situation.

Why is it important?
The point is:
 arrangers and composers tend to work in a much more chaotic unpredictable
way than one could think. 
It's not uncommon for me and my colleagues to be switching between different
modes every few seconds, moving things around doing lots of copy and paste,
re-editing lines back and forth e.t.c.  
Actual note input is a comparatively small portion of that process (maybe
30%). 

Having a  coherent editing workflow is crucial for this kind of work and I
would say the more complex the process is, the more predictable and
straightforward program's behavior should be in any mode. 


Hope this is useful and not overly critical. 

best,

Anton



--
View this message in context: 
http://dev-list.musescore.org/Ties-Behavior-tp7579781p7579794.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to