Clars,
While I obviously fully understand the problem, here's one way to
think of using a parent script. Take any code in your "master"
behavior that doesn't deal directly with putting sprites on the
screen, and make a single global object out of it. So, move things
like your folder info, file count, sorting, FileIO code, etc, into
this single master object. Whenever there is interaction, (e.g., the
user presses a next or previous button), call a handler in the Master
object. The Master object can decide what to do with that (like go
to the previous page) and then use "sendSprite" to talk to any screen
sprite that needs to be updated.
Basic approach is that each behavior is only responsible for doing
what it needs to do individually, and potentially report to the
Master object. The Master object is responsible for issues that
affect multiple sprites. Kind of like a "manager" in the business
world.
Hope this helps - or at least gives you a direction,
Irv
At 11:04 PM +0100 12/15/00, Clars wrote:
>
>
>-Maybe. The project is basically a digital photo album, where I can view
>the image files in a folder, in fullscreen, as a list, or as thumbnails.
>I can associate comments (stored in a database) with the images.
>
>The behavior is attached to a text member which holds the names of the
>files. This behavior is a master for two slave text members which hold
>the date/size of the files.
>
>The behavior properties are things like the folder path, the current
<snip>
--
Lingo / Director / Shockwave development for all occasions.
(Over two millions lines of Lingo code served!)
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
