Nevermind. I found the "Relaunch Sampler.rev" stack referred to in the
Dictionary entry and it explains how the message is used further.
On 5/8/2022 12:08 PM, Paul Dupuis via use-livecode wrote:
The LC 9.6.7 Dictionary entry to 'relaunch" states:
It can be used in the following three ways:
The LC 9.6.7 Dictionary entry to 'relaunch" states:
It can be used in the following three ways:
|1. If the message is passed, then the new instance continues running.
2. If "background" is returned, then the new instance is terminated. 3.
If nothing is returned but the message is not passed,
On 5/8/2022 11:47 AM, Colin Holgate via use-livecode wrote:
I wonder if the relaunch approach would leave the user in File Explorer, and
would not switch across to the existing app instance? Hopefully it will be that
simple.
If it isn’t, try this approach:
On 5/8/2022 11:37 AM, Klaus major-k via use-livecode wrote:
just add this "dummy" handler to your stack:
on relaunch
## Nada :-)
end relaunch
-
That will prevent the launching of multiple instances on Windows!
Thank you! I was
I wonder if the relaunch approach would leave the user in File Explorer, and
would not switch across to the existing app instance? Hopefully it will be that
simple.
If it isn’t, try this approach:
https://use-livecode.runrev.narkive.com/wOjpGm5V/external-for-running-one-instance-on-windows
>
Hi Paul,
> Am 08.05.2022 um 17:32 schrieb Paul Dupuis via use-livecode
> :
>
> Seeking help:
>
> On MacOS when you try to launch a second instance of an application, the
> macOS just brings the open app to the front (for example, if it is hidden on
> minimized).
> On Windows, when you try to
Seeking help:
On MacOS when you try to launch a second instance of an application, the
macOS just brings the open app to the front (for example, if it is
hidden on minimized).
On Windows, when you try to launch a second instance of an application,
Windows launches a second (or 3rd or 4th or
