LightsOut.DLL external

malkishtini at malkishtini at
Fri Jul 22 13:01:46 UTC 2022

Hi Doug,

Thank you for sharing your hint, I have not even thought about it before :). Since we are still very busy with the conversion process, we just look for readymade stuff to help us solve side issues.
But I can investigate adding a timer to the system and test it.

But just in case, do you have the email of Kelly Burgess? 

Thank you,

-----Original Message-----
From: omnisdev-en <omnisdev-en-bounces at> On Behalf Of Doug Easterbrook via omnisdev-en
Sent: Friday, July 22, 2022 8:52 AM
To: OmnisDev List - English <omnisdev-en at>
Cc: Doug Easterbrook <doug at>
Subject: Re: LightsOut.DLL external

hi Mayada

you’d have to ask kelly.

The difference between classic and studio is that classic had one timer, as I recall.

so, in classic, you needed to use that one timer to handle many different things and write conditional code to decide which thing you were timing.    or, in other words, you only had one timer loop.    Lightsout enabled you to have many (we used it and relied on it - it was a godsend)

in Studio, you can make many timers and timer objects.   It makes it much easier to make an independent lightsout style timer that fires at a specific time - using native studio timers.

in other words, what you are trying to do is easy with built in studio timers.

Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at
Phone (403) 650-1978

> On Jul 22, 2022, at 5:36 AM, malkishtini at wrote:
> Good day list,
> In classic we use an external called "LightsOut.DLL" to shut down all 
> the running Omnis instances at night.
> Does anyone know if there is a similar XCOMP or an external in studio 
> that can be used for the same functionality?
> Thank you,
> Mayada
> _____________________________________________________________
> Manage your list subscriptions at Start a 
> new message -> mailto:omnisdev-en at

More information about the omnisdev-en mailing list