> Add new NotationPreview class.
>
> This is a work in progress. Committing it for a backup. I'm trying to
> pull the notation preview concept out of CompositionModelImpl. This
> is one of the areas that uses excessive CPU time.
Does it ever! Before I optimized segment setStartTime, it was (then)
calling out for an absurd number of redraws. A single range insert
resulted in something like 30,000.
Segment tends to call for a large number of unneccessary redraws, due to
using functions that are really meant to insert or remove one single event
and then clean up everything so it's perfect and ready to go.
Good that you are tackling this, Ted.
> + * One key question is whether this class
> + * should handle a single segment, or all the segments in the composition.
> + * Not sure which results in the simpler implementation. Handling a
single
> + * segment means the client would need to manage a collection of these
In my experience, RG is mostly calling for redraws on a segment-by-segment
basis. That alone may make it simpler to handle it segment-by-segment.
It might (just my educated guess) make sense to make it a segment observer
and augment the segment observer interface with efficient group
operations, and make Segment use those when it can. When I did that, it
was easy and worked well.
Tom Breton (Tehom)
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
