I'd like to make the velocity dialog smarter. For instance, when you make
a crescendo, the start velocity would default to the lowest velocity among
the selected events and the end velocity to the highest.
But the way EventParameterDialog works makes it difficult to do so. It
doesn't see the selection. Right now it couldn't because it's trying to
be a general note-property editor too. AFAICT it's not used for anything
but velocity now and my change would actually make other uses somewhat
easier.
So I'm asking, is anybody attached to the way it works now?
What I'd like to do is factor out the velocity smarts into a helper class.
That class would know the selection and other info. EventParameterDialog
would just know the widgets, and would get text etc from the helper class.
The two existing callers of EventParameterDialog would create that class,
pass it to EventParameterDialog, and when done, pass it to
SelectionPropertyCommand (which is used just for this and two lighter
velocity commands. I'd adapt all four callers).
Having done that, then I could make the dialog get smarter initial values,
etc.
Tom Breton (Tehom)
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
