You're all talking about stopping SalTimer because of paint handling.
This is not correct at all, SalTimer is the central mwthod for Timer
base stuff in the whole of OOo - the paint timer is just one Timer of
many. So simply not implementing SalTimer will not gain you much, the
office will not work very well since so much of it is timer based. If
you want to disable the timer based paint handling you'll have to look
in vcl/source/window/window.cxx where (sadly in the independent part)
where you can disable the asynchronous paint handling.
However this is only the tip of the iceberg. Applications can and will
paint whenever they want to - usually as a reaction to other events like
focus, button clicks, mouse movements, whatever. Throughout the office
we will have to change these places to call Window::Invalidate instead
of painting directly; and of course Invalidate will need to be forwarded
to the system itself which it currently is not - I assume that there is
a method on MacOSX to trigger a paint event through the system.
As a start of course one can make the paint handling in window.cxx
synchronous.
Don't get me wrong, I think that nowadays it would be a great advantage
if paint were only done in the paint callback, not only on MacOSX, but
on Windows as well (on X11 platforms this problem is irrelevant since
all real painting is done in the Xserver anyway which is another
process). For example synchronous painting would have saved AW tons of
pain when implementing his overlay buffer stuff. It's only that this
cannot be achieved at a central point. For a while we'll have to live
with this behavior and remove the "out of order" paints step by step.
The painting in window.cxx is certainly the best first step to do this.
Kind regards, pl
eric.bachard wrote:
> The first try Sébastien and me did with HIView and compositing, let us
> think redraw can probably be correct without such features to be used.
> But I can be wrong. Or do we use that because it is in common part, and
> because other architectures -Windows probably- use it or .. ?
> P.S. : Ismael suggested a Google YEAR of Code to fix that :)
Yes, that's about the order I'd imagine ;-)
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
