> It just hides a fake segment. If the user is in a position to use it, > he's already done the obscure, highly advanced stuff. Now he's just > hiding something he's looking at.
There are probably fewer than ten people on the planet who have any idea what the ornament feature is for, so it's automatically in highly advanced territory. > That's always been the case, so I don't think that changes how anything > works. That's not to say that no commands mess up tie properties, just > that I don't believe this creates new problems on that front. Only by way of making it possible to avoid selecting all the notes in a tied series. > FWIW, after what you said I took a look at SetNoteTypeCommand and > AddDotCommand. Regardless what selection tool is used, they seem to think > every note is untied, just plopping new events directly into Segment. > This may be the source of some of your headaches. I might as well add a > fix for that now. That works. The problem is when you grab something with tied forward/backward properties without getting all the interrelated events at the same time. Strange things can happen, because a note is supposed to be tied but can't be tied, because it has no mate(s). This was especially a problem in the matrix, where there was just simply no way to know the events were tied at all, and that was the main motivation of making selections grab all the notes in a tied series, and forcing the whole thing to behave as one unit. -- D. Michael McIntyre ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
