I'm not sure what you're saying here. I agree having chords with partial
ties is normally not what one wants. And that's precisely why I was saying
I was uncomfortable with making the tie command a toggle, as that would
make it harder to correct the situations where this happens currently.
Right now, if you inadvertently create a partially tied chord (and it's
easy enough to this in the normal course of editing), you can fix it by
selecting the whole chird and pressing the tie button. This leaves the
existing ties alone but adds new ones. I'd hate for that easy fix to be
made harder. But making the tie command a toggle would have just that
effect, unless we were very careful in implementing it to only work as a
toggle if all selected notes have the same tie status. That's certainly a
possibility.
On Mon, Apr 11, 2016 at 2:58 PM antonjazzsax <antonjazz...@ukr.net> wrote:
> Marc Sabatella wrote
> > The downside of changing the tie button into a toggle is that it becomes
> > potentially harder to handle chords well. Currently you can use the tie
> > button to easily add ties to notes in a chord without affecting existing
> > ties. If we changed the tie to a toggle, you'd potentially end up adding
> > ties where they were missing but deleting them where they already were,
> if
> > the whole chord were selected.
> > Marc
>
> The thing is, you don't want to have chords with partial ties. That is
> something from a real world practice: If you are writing a chord where the
> middle voice is moving and other are sustained you are basically asking for
> trouble. Players gonna miss it 8 times out of 10 when sight reading. The
> proper way would be to split notes to different voices.
>
>
> Marc Sabatella wrote
> > If we made this only work while in note
> > input mode, then it wouldn't be so bad, because you can't generally
> select
> > a whole chord while in note input mode.
>
> Please don't do that! Surely there will be some loyal MUS followers who
> will
> get used to that working routine, but the majority of new users will want
> to
> have their most used commands to work globally.
> I know that this is not exactly how your program is designed but for the
> practical use, people gonna want it dumb-proof,
> one-command-works-everywhere
> kind of layout. Ask other people's opinion.... see what they say.
>
>
>
> --
> View this message in context:
> http://dev-list.musescore.org/Ties-Behavior-tp7579781p7579807.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!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
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!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
