On Monday, October 10, 2011, cjnf wrote: > Wasn't there an "observer" mechanism of some sort to notify the rulers > of segment changes? If I recall correctly, it confused the hell out of > me when I first saw it but was pretty elegant. Something like the ruler > would inherit an observer class and register itself with the segment on > creation. The segment keeps a list of observers and calls their > segmentchanged method when something changes ... or some such.
That sounds about right, actually. I've never done any work that involved using that mechanism, and so I've never understood it very well. It could well be that making Segment a QObject is reinventing the wheel, and this was supposed to be accomplished using the SegmentObserver mechanism. I find that I'm pretty ambivalent about how things get done as long as they work. -- D. Michael McIntyre ------------------------------------------------------------------------------ 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-d2d-oct _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
