This content has been marked as final. Show 5 replies
Actually, script objects attached to sprites, are.. well.. objects.
There does exist an overhead when calling a sprite instead of the script
object directly, especially if more than one behaviours are attached to the
sprite, since director has to figure what object's handler to call, but I
doubt it's even measurable.
If I may ask, why is speed so crucial for an audio application? I can
understand filter processing time, but what does that have to do with
objects? Or is it about visualization, meters etc?
"www.gamesmaken.pagina.nl" <firstname.lastname@example.org> wrote in message
> I am working on a project where i do not really need to implent OOPS
> programming. However speed is a ver big issue, as it is an audio
> Now, can i expect a significant speed improvement if i write the
> using object oriented scripting rather than attaching scripts to sprites.
> Is it
> possible to say something general about this?
>>Is it possible to say something general about this?
Yes, generally OO programming techniques are meant to allow code to be
portable, extensible, and manageable. If you want fast code you still need
to optimize and write good code, which doesn't have a whole lot do do with
Adobe Community Expert
thanks. It is a realtime audio-midi application. In music any milisecond is audible, thats why i need all the speed i can get.
read the open source manual on projectmanagement:
Never mind... there is an english version of the book.