Um, although I spent a lot of time on the history, I'm pretty sure my first 
sentence said "its main value is to set up some global variables before the 
start of the movie".

In fact, I don't think you even need to declare them global, because if I 
recall correctly, all variables addressed in there are automatically 
considered global.

And, yes, I know globals are good throughout and across movies.  That's why 
they're called "globals" :)

- Tab


At 05:38 PM 4/18/01 +0100, Karina Steffens wrote:

> > Nowadays you don't really need LINGO.INI, at least from D7
> > on, but it's
> > there if you want it.
>
>Sorry Tab, I have to disagree with that bit... There's an excellent usage
>for the lingo.ini file, as a companion to a fast-start "universal
>projector".
>
>Have a look at this handler:
>
>global gfMovie
>
>on startUp
>    gfMovie = "Main"
>end startUp
>
>and this handler:
>
>global gfMovie
>on startMovie
>   go movie gfMovie
>end
>
>The first will go into the lingo.ini file and the second one will go into a
>stub director movie that's compiled into a fast-start projector - with
>nothing else in it. The moment you double click the projector, it will open
>a movie called "movie". Then, you can just copy and pase your projector,
>lingo.ini file and extras folder into any director project folder and all
>you need to do is open the lingo.ini and change your gfMovie handler into
>whatever you want.
>That will save you making seperate stub projectors for each project.
>A note: it has to be saved as a global, because you can't execute a "go to
>movie" command from the lingo.ini
>
>PS: You can also use it to define other globals for usage in any of your
>movies (not just the stub - globals carry over across movies unless
>"clearGlobals" is used)
>
>
>Karina


[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!]

Reply via email to