On Thursday 10 July 2003 3:36 pm, Chris Cannam wrote: > Calling repaint() doesn't necessarily force the rulers to repaint -- > they can just look up their refresh status (for composition or > segment changes) and repaint only where necessary.
Um, hang on. I was just talking about QWidget::repaint() (or sim) that will definitely repaint a widget. I think perhaps where my confusion is coming from. We also have a Rosegarden::repaint() which is predicated by a refresh status. So that's a different kind of repaint() to just a Qt repaint which will just happen. > We obviously don't want to have things repainting when we're not even > in the event loop yet -- waste of effort -- but a central thingy that > knows just to call repaint() on everything visible as appropriate > (instructing them to go off at the next event loop and check if > anything's really changed) might work nicely. Again, I'm a bit confused. Surely if we're executing QWidget::repaint() then the painting will occur at the next event loop anyway or it'll be taken care of by something inside Qt or X11? Or am I missing something fundamental about either Qt or X11? Perhaps this part of the argument is being overcomplicated by the fact the Segments/Events are distinctely numerous and that the rest of the stuff we'll be bothering with re: updating the GUI isn't that huge and therefore we don't need to worry about refresh statuses as much or optimising the repaint()/whatever) before we've got it working. Put simply we want a document-centred thing we can connect dialogs and gui components through that doesn't intrinsicly care too much about how much repainting is going to go on. Second part of the original question - if we want this driven through Commands then where do we hook it up to the existing mechanism? At the moment I know that if I modify Segments/Events as part of a command then views will get updated but I can't see where the magic is happening. Obviously through MultiViewCommandHistory somewhere but where? R ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
