On Thursday 12 June 2003 22:07, Chris Cannam wrote:
> Well, the obvious reason I'm looking at this at all (apart from that I
> think the current design is basically wrong in the one or two ways)
> is that I've been trying to get to the bottom of a rather serious
> crashing bug.
I understand. But my design boils down to this :
1. the ruler has to offer fairly involved interaction with the user. It
doesn't just display things, so the best way to do it is with a QCanvas.
2. A QCanvas means computing the layout of all the elements at once, not just
those in the displayed timeframe like with the other rulers. I can do this in
two ways :
2a. Do a layout of the elements like with any other edition view
2b. Take advantage of the fact that the layout is already being done and the
info is available.
The main problem with 2a is performance. Layout can take time, and it will be
possible to have several control rulers for several properties, so that
wouldn't scale very well.
2b solves this, but at the expense of, well, more code.
But in the end, you have the Composition, which is being watched by the
Edition Views, which are being watched by the Control Rulers. It's not *that*
ugly, really.
> Anyway, I'm half way through this change, but what I'll do is send a
> patch to the list when I'm finished rather than committing anything.
> Then we can debate the pros and cons of that.
Fine with me.
--
Guillaume.
http://www.telegraph-road.org
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
