fenfire-dev
[Top][All Lists]
Advanced

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

Re: [Fenfire-dev] Repost^5: PEG animation_api--mudyc


From: Tuomas Lukka
Subject: Re: [Fenfire-dev] Repost^5: PEG animation_api--mudyc
Date: Fri, 7 Nov 2003 14:52:22 +0200
User-agent: Mutt/1.5.4i

The only remaining problem is naming.

On Fri, Nov 07, 2003 at 02:43:26PM +0200, Matti Katila wrote:
>          * @see VobMatcher
>          */
>         void animate();
> 
> 
>         /** Switch to next VobScene by creating a new VobScene.
>          * The switch is fast and no animation is seen. 
>          * This method is pending, i.e., next screen update is soon 

"This method is pending" is not really the right way to say
it but let's edit that later. 

>          * but not immediately.
>          */
>         void switchVS();

Why animate() but switchVS()?

Why not animateVS() or just switch()?

Or maybe update_animate() and update_abrupt()?

>         /** Rerender the current VobScene. 
>          * This method is pending, i.e., next screen update is soon 
>          * but not immediately.
>          * <p>
>          * Changes in next frame are seen if coordinate system
>          * parameters are set. Rerendering the current VobScene 
>          * is much faster than creating a new VobScene, 
>          * so e.g., any drag actions should be implemented to use
>          * this method. 
>        * <p>
>          * Implementation note:
>          * <ol><li>
>          *  Even though new coordinate systems can be created, the current 
>          *  coorder implementation uses finite range of coordinate systems. 
>        *  Creating too many new coordinate systems leads to
>          *  undefined behauviour.
>          * </li><li>
>          *  If there's a vob which needs to be removed,
>          *  it's usually faster to set coordinate system parameters 
>          *  to zero than generate a new scene without the accursed vob.
>          * </li></ol>
>        * @see VobCoorder
>          */
>         void rerender();

Same here?

>       /** Get the current visible vobscene. 
>          * <p>
>          * Prgogramming note: When programming, you create vobscenes
>          * for future usually, so this returns the current visible
>          * vobscene, e.g., to set coordinate system parameters or 
>          * use activated coordinate systems to catch mouse events.
>          */
>         VobScene getCurrentVS();
> 
> 
>       /** Returns true if there are pending methods that 
>          *  create a new VobScene which has not yet been updated
>          *  within window. The methods that create a new VobScene
>          *  are <code>animate</code> and <code>switchVS</code>.
>          * <p>
>          * Programming note:
>          *  In some situations when handling the events the programmer 
>          *  needs to know whether the VobScene is new or the still the old 
> one,
>          *  e.g., when waiting to move some new vob you
>          *  you need to pass all events trough before the screen has updated.
>        */
>       boolean hasSceneReplacementPending();

And this really should be "isSceneReplacementPending()", I think.

        Tuomas




reply via email to

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