gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash/gui gui.cpp gui.h


From: strk
Subject: Re: [Gnash-commit] gnash/gui gui.cpp gui.h
Date: Fri, 3 Nov 2006 23:10:10 +0100

On Fri, Nov 03, 2006 at 04:39:40PM +0100, Udo Giacomozzi wrote:

> >> +    /// Signals that the next frame must be re-rendered completely 
> >> because the
> >> +    /// window size did change.
> >> +    bool            _redraw_flag;
> 
> s> I would omit the *reason* if we allow arbitrary reasons to completely
> s> redraw (for example expose event received)
> 
> We discuss this already in another thread. However, the point was
> /not/ to /force/ a redraw on each resize event. The reasons are the
> same as for the button events (trigger redraw on each mouse move
> event?).

mmm... I don't like GUI events to be driven by frame rate.
I think movie events should be handled like user event (ie: when
they happen). Colin Moock in his book refers to event as divided
in "user" or "system" events.
System events include 'enterFrame'. I guess we might add 'window expose'.

Consider a movie at very low frame rate, do we really want to wait
for next frame before redrawing a just-raised window ?

Yes, each Gui might implement this internally, but what would the
point be for the above _redraw_flag then ?

--strk;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]