I'm sure this has come up before.
I'm trying to come up with a bullet proof method of preventing our users
from openning multiple instances of our projectors in Windows.
I've looked in the Direct-L archives and have tested two methods already:
Bruce Epstein's "ini" file "singleInstance" setting; and using BudApi to
have each instance look for previous instances and quit itself if a
previous instance is found.
The "ini" file "settings" method does prevent multiple instantiation, but
it can leave the Windows interface on top of our program. The program is a
series of kids games and is designed to run full screen. The projector is
compiled for full screen, plus I use the "fullScreen=1" setting in the
"ini" file. Even with these precautions, fast clicking on the projector's
icon will cause the program to open up as a minimized window in the
Windows task bar. Maximizing the program from the task bar works, but
leaves the task bar on the screen. This isn't acceptable for a young kid's
game suite.
The second method (using budAPI to check for previous instances and then
quitting if one is encountered) works sometimes, but often *all* the
instances will quit. Again this is confusing for our age group of users
(very young).
Anyone have other suggestions?
Many thanks in advance!
Matthew
Matthew Kaplan
Chicago
[EMAIL PROTECTED]
[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!]
