Windows 7 and LC 7.1
SKIP
On Wed, Oct 28, 2015 at 5:17 PM, J. Landman Gay
wrote:
> It also happens if there are any drivers that weren't closed.
>
> On 10/28/2015 3:45 PM, Magicgate Software - Skip Kimpel wrote:
>
>> Nope, no timers pending. This is consistent across ANY Windows standalone
>>
It also happens if there are any drivers that weren't closed.
On 10/28/2015 3:45 PM, Magicgate Software - Skip Kimpel wrote:
Nope, no timers pending. This is consistent across ANY Windows standalone
I create.
SKIP
On Wed, Oct 28, 2015 at 4:32 PM, Richard Gaskin
wrote:
Skip, do you have any
Which LC version, and which Windows version?
~Roger
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-liveco
Nope, no timers pending. This is consistent across ANY Windows standalone
I create.
SKIP
On Wed, Oct 28, 2015 at 4:32 PM, Richard Gaskin
wrote:
> Skip, do you have any timers pending?
>
> --
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, a
Skip, do you have any timers pending?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.comhttp://www.FourthWorld.com
___
Thanks Roger That is the same strategy I have been using as well but
this must be an oversight on LC's side as it is really annoying!
Thanks again,
SKIP
On Wed, Oct 28, 2015 at 4:09 PM, Roger Eller
wrote:
> I used to see that quite often until I started including this in the stack
> script
I used to see that quite often until I started including this in the stack
script of the main stack.
on closeStackRequest
close this stack
quit
end closeStackRequest
~Roger
On Wed, Oct 28, 2015 at 4:01 PM, Magicgate Software - Skip Kimpel <
s...@magicgate.com> wrote:
> Has anybody notice
Has anybody noticed that when you build a standalone now for Windows, if
you click the native "X" to close out the application, it looks like it is
gone, however it continues to run in the background and has to be killed
using the Task Manager?
They has been happening for the past few releases and
