I've just started using Lingo.ini. In it you can do some minor Lingo
like setting globals. For example, I have a Lingo.ini file that
looks something like this:
on startup
global gProductAbbreviation
gProductAbbreviation = "RA"
end startup
Then I have a "stub" projector that looks like this
global gProductAbbreviation -- comes from <Product>.ini file, MUST
be set correctly there!
on exitFrame me
myMoviepath = the moviePath & gProductAbbreviation
go to movie myMoviepath
end
This way, I use my stub projector to start a movie called RA.dir (or
RA.dxr). But by just editing Lingo.ini, I could use my stub
projector to start any movie.
Another good use would be to set some debugging information:
on startup
global gDebugState -- could be VOID, #low, #medium, #high
gDebugState
end
Then in your program, when an error occurs, you could have a routine
that you call to do something depending on the debugging state that
you've set.
Irv
At 7:37 PM -0800 2/12/02, mike cash wrote:
>Greets, I've been programming with Director (PC) for many years
>now...but have never used an ini file with any of my projects. What
>am I missing by not using that feature?
>
>Or, more simply put, what are you using the .ini file for?
--
Lingo / Director / Shockwave development for all occasions.
(Home-made Lingo cooked up fresh every day just for you.)
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/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!]
