On 17 April 2018 at 00:11, Peter Uhnák <i.uhnak@gmail.com> wrote:
On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman <btc@openinworld.com> wrote:
On 16 April 2018 at 16:55, Peter Uhnák <i.uhnak@gmail.com> wrote:
Downloaded it. Installed it. Started it. Selected an image. Bam. The app vanished.
As I've mentioned in several other threads, the way new images are opened (the lib that executes the command) seems to be very unreliable and sometimes opening image just doesn't work, and I have to open PL again and try again.
My guess is that there's a race condition and PL closes faster, and before the subprocess manages to be disowned.
I untick the box "Quit on Launch"
That just turns the problem of "I sometimes have to do extra steps" to "I always have to do extra steps" (i.e. close PL)
You misunderstand. I *prefer* never to close PharoLauncher. Particularly when I dig deep into stuff that is likely to hang an Image, Needing to *again* click the start menu, then click PharoLauncher, to get to the Image I want are two extra steps I like to avoid. I guess thats why I added that feature to PharoLauncher ;) cheers -ben