I just committed code that makes the Matrix editor update the velocity
ruler. It's a pretty small change; most of the work was in ferreting out
the exact parts that needed the change.
One compromise I made that's less than ideal: updating PropertyControlItem
now causes an extra update of MatrixElement.
ISTM the proper alternative would have meant giving MatrixElement logic to
only update when dirty, which means it would need to know when Event is
dirty, which implies that both would need some sort of timestamp (or
tickstamp). That would either be inconsistent with the way other views of
events are drawn or would imply changing them too. That'd be a big
change, certainly not something I should launch myself. So I didn't.
Other details:
* Segment now derives from QObject; Qt insists on it being the first base.
* Segment now has a signal, contentsChanged. Contents-modifying commands
cause it to emit that signal. That's done thru BasicCommand, so I
suspect that includes all the relevant commands.
* That signal connects to rulers visiting the segment via
ControlRulerWidget.
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
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
