If you look at the script i posted before, then you see for windows /T
and /F and so on.
This will kill the application and all child processes.
On 23-05-19 17:59, Bob Sneidar via use-livecode wrote:
So this seems odd to me. If an executable that spawns other processes/threads
(if that is
So this seems odd to me. If an executable that spawns other processes/threads
(if that is what a splash stack is doing) quits, Windows should also terminate
the processes/threads.
I suppose, from reading various email posts here that there are different ways
to implement a splash screen. As I
Actually, this all seems like a Windows "bug" to me.
A language like LiveCode, should, if I script 'quit', do exactly that -
quit. If there are any open anythings preventing that, the engine should
shut them all down for us.
Now as a software developer, I agree that good programming practice
It's not just fonts, anything that's still in use needs to be removed.
Fonts, stacks in use, open processes, com ports, sockets, etc. Basically
you need to shut down everything the stack opened.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software |
If it is a requirement for any loaded fonts to be unloaded from memory
for a Standalone to actually quit under Microsoft Windows then a bug
should be entered at https://quality.livecode.com/ to update the
Dictionary entries for:
closeStackRequest
shutDownRequest
quit
start using font
stop
I do this to cleanly exit my Windows standalone, which is a splashscreen stack.
Because I have used a couple of fonts that I keep with the standalone, I have
to STOP USING them, else the process will still continue to run.
This handler is in my visible stack, not in the standalone splashscreen
i use this which works ok on windows but hangs on Macos(when clicking
the red x, it works when going to quit via the menu, i don't know why)
if the environment is "standalone application" then
if the platform is "Win32" then
--added /T and /F, /T Terminates process and any child
NVM Apparently I am supposed to use lock messages to force a quit. There may be
something in my code that is halting the quit process, but I don't really need
to do any housekeeping, so this works.
Bob S
> On May 17, 2019, at 13:37 , Richmond via use-livecode
> wrote:
>
> As your splash
Need a speel chekr.
I meant to say, "...but it doesn't quit. It tosses an error and the processes
continues to run.
Bob S
> On May 17, 2019, at 13:43 , Bob Sneidar via use-livecode
> wrote:
>
> but it doesn't wuit it tosses an error and the precess continues to run.
The Splash Stack has the mainstack in it's stackFiles. The actual mainstack is
the application the user interacts with. But by the time a standalone is
created, there are not mainstacks/substacks.
So the Splashstack is the standalone, which then opens the mainstack and gets
the ball rolling.
As your splash stack is, presumably,either a substack of your main
standalone, or the main stack itself
I don't think you can exit it without the whole standalone exiting.
So, I suspect, you'll have to find another way of getting the splash
stack out of the way.
Personally I'd make the
Hi all.
I have a splash stach in a Windows Standalone. When I close (or otherwise quit)
the stack which the splash stack opens (the actual application) I get a runtime
error, and the Splash process continues to run.
What is the proper way to cleanly exit an app of this nature?
Bob S
12 matches
Mail list logo
