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, f
Irv Kalb wrote:
> Wow, an entire discussion on OOP, and I'm out of the office for one
> morning.
-Sorry you missed out on all the fun!
> One quick comment. In your original message you mentioned that there
> were five different properties that you wanted to get and/or set from
> a behavior.
At 8:27 PM +0100 12/15/00, Clars wrote:
>Thanks again for input, all.
>
>Karina - any sources for naming conventons? I use p for property and g
>or m for global variables(project global or movie global), but that's
>about it.
>
>Jakob- I sent my post before I read yours. I suppose that specificall
Thanks again for input, all.
Karina - any sources for naming conventons? I use p for property and g
or m for global variables(project global or movie global), but that's
about it.
Jakob- I sent my post before I read yours. I suppose that specifically
writing seemingly redundant access handlers g
