Hello Michael,
I just noticed this commit log message:
> Adjusting the start/end of the selection _was_ very
> necessary. The various
> commands that cut and so forth use these boundaries as
> their start/end points
> for iteration, so any events contained in the selection
> that are outside the
> boundaries don't get included properly. I'm not
> actually sure why the
> selected-but-not-highlighted notes were even cutting at
> all. No matter, this
> seems to have done the trick on sorting out all of that
> score.
I see you are adjust the start and end times.
I haven't tried this yet, but I think we are going to run into issues here when
people have intentionally shortened segments and hidden events.
I couple moths ago I just spent a week unravelling all of the mess-ups related
to the end of composition and segment shortening.
Please make certain that these segments you are altering are no t magically
re-extending their segment length.
I think it would be annoying to have my segment length change because I
selected a tied note that was tied to a note I was trying to hide, or somehow
forcing a segment passed the length of the composition.
I forget the details at the moment and don't have time to investigate.
But please go slow here an check for side effects concerning segment length:
Intentional shortening getting undone, and trouble with end of composition
stuff.
Good luck on the tied note thing -- round II it looks like.
Sincerely,
Julie S.
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
