Hello Michael,
> > It's true that this can get complicated. Even to
> get this one instance
> > going took a bit of re-engineering.
>
> When I was messing around earlier, it really struck me that
> having the
> selection evaporate after adding a mark was pretty
> irritating.
I'm not seeing that happen. I can make a selection and apply marks (in svn and
Classic).
> It makes me think about what I did to stop the newly
> inserted slur from being
> selected. It was some eventsToInsert kind of thing
> like something I just saw
> in your commit, and I think I commented it out.
Now when I do things like add a slur to a selection set of a hairpin (crescendo
/ decrescendo). I get that annoying behavior you talk about. In Classic the
newly inserted item is selected and the old selection is lost. In svn we just
loose the selection entirely.
>
> It was a huge improvement for what I was doing at the time,
> but I suspect I
> didn't think it through thoroughly enough. Since
> you're of a mind to think
> about stuff like this, you might take a moment to survey
> the different ways we
> behave in this area, and get us started thinking about some
> plan for enforcing
> consistent behavior everywhere.
Yes, making a list of these kinds of quicks along with a bit of background of
current state of the related code could give everyone a chance to weigh in on
how to proceed. From preliminary work on this little issue (which I'm not 100%
satisfied with it solution) I do have some ideas about how to proceed.
>
> I have a very solid and passionate sense that I did the
> right thing with the
> new selection behavior that makes tied groups behave as
> single units,
Yes, it was the right things to do. They are indeed a single unit (musically),
if people need to place articulations, fingerings, or ornaments on the other
not or make a break to easily place a set of hairpins, etc. They can just slur
the notes. I know its not technically the same, but will convey most of the
real meaning.
> but I
> don't have much of a sense of the rest of it at all.
> I could use some fresh
> eyes who aren't so used to and accepting of working around
> all these
> irritating quirks.
As long as slow is okay. I really don't want to get pressed by a hypothetical
release date. (I still need to go back and clean up those progress bars that
were barely half finished before the last release).
> On a related topic, it would be good to make undo remember
> what the selection
> was at the time. I have no earthly idea what I'm
> proposing in code terms,
> because I haven't thought about it at all. I'm just
> thinking of all the times
> I composed some carefully crafted selection, applied some
> effect, reverted the
> results, and then had to compose the entire selection again
> to try a different
> effect. I wonder what it would take to fix
> that. It's incredibly irritating.
Hmmm....sorry, not gong to bite on that one. I think undoing and redoing
selections is pretty tricky.
Alternatively, It would be very handy to at least recall the last selection
though...that might be an easier goal. That way you could at least get at the
selection after an undo or if you accidentally started a new selection while
building you that hand crafted selection set. But now we are getting into
feature request territory.
I'd prefer to stick with trying to get what we got working better and leave the
fun new features to those with ambition for that thing. I'm still of the
mindset that RG is a bit broken all around, and would prefer to stick with
making what we have function instead of adding to it. It seem to be the work I
do best and isn't the typical fodder for most -- except for you and I.
Sincerely,
Julie S.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
