[Papervision3D] Single vs. multiple onEnterFrame

[Anthony Tambrin]

I see :) John, basically you're saying centralized onEnterFrame is good for
processing that don't depend on scopes, which is quite the case given one's
preference of coding in AS3. Felix, I'd be interested to see some concrete
data on those difference, even if it's really small. I'm thinking of doing
some benchmarking little app for this purpose and post the app on the forum,
hopefully by end of this week.

Cheers,
Anthony


On 4/2/07, John Grden <neoriley at gmail.com> wrote:
>
> when the playhead changes frames, all registered onEnterEvent listeners
> are fired.  I think the reasoning for individual EnterFrames would be based
> on scope and control of the object itself, but if it's something that has to
> happen at the same time and scope isn't an issue etc, might as well put it
> in one method.
>
> my 2cents based on what I think you were asking ;)  (that's my disclaimer)
>
> On 4/1/07, Anthony Tambrin < copet80.mailinglist at gmail.com> wrote:
>
> > Hi all,
> >
> > This is more of a general flash question. But I reckon it's the heart
> > and soul of pv3d applications :)
> >
> > Question is:
> >
> > Which one is more efficient?
> > A. All processing is centralized in the main Sprite ENTER_FRAME event
> > handler, i.e. run()
> > B. Objects have their own ENTER_FRAME event handler
> >
> > Which one will run more efficiently, and thus, faster?
> >
> > Cheers,
> > Anthony
> >
> > _______________________________________________
> > Papervision3D mailing list
> > Papervision3D at osflash.org
> > http://osflash.org/mailman/listinfo/papervision3d_osflash.org
> >
> >
>
>
> --
> [  JPG  ]
> _______________________________________________
> Papervision3D mailing list
> Papervision3D at osflash.org
> http://osflash.org/mailman/listinfo/papervision3d_osflash.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/papervision3d_osflash.org/attachments/20070402/efe4568e/attachment-0001.htm