ah thank you . If it's common praftice I will omit that from a list of things wrong with this.
> I may not be understanding it correctly, but I know one common > convention for Flash was to group all actionscript in a layer of it's > own so as to not have little bits of code in different frames, > different layers which quickly becomes a PITA. > > Also, the OO aspect of it could be two fold. Your first way, or it > could be that the button announces an event and the event is acted > upon by a "controller" object/script. > > > > On 4/15/07, Dana Tierney <[EMAIL PROTECTED]> wrote: > > I inherited a Flash app that ... well, never mind. I've been given > permission to start from scratch, but to meet an institutional > objective, this one does need to be put in some sort of functionality > first. I guess it's not wasted effort if I am learning what to do and > not do from it. > > > > So I am mano e mano with the script now and what I am wondering is > this -- if there is code whereby an object does something (a button > takes you to the next slide for example) would OO not imply that this > code should be on the layer where the object is? In Actions maybe? > Right now it's about 30 pages of script in its own layer. Is there a > reason to do this that I have not yet understood? > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:232579 Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5
