Hi - thanks for suggesting that. It’s actually set to true - and on OSX 
Mavericks, with that setting it seems that when I launch a new image (and it 
supposedly quits) - when I run the launcher again - it just takes me to the 
image that was just launched. (I swear it didn’t do that at some point - and 
I’m not sure if its since I updated to Mavericks - or whether my other OSX 
computer doesn’t exhibit this behaviour).

Anyway - if I uncheck it (and leave the launcher running) - then I can at least 
launch other images (and if I run the app again - it seems to bring the running 
launcher to the foreground). If I try and quit the launcher manually after 
launching an image - it still exhibit this same behaviour. It’s quite strange? 
(but at least I have a workaround).

By the way  - do you know how you save that setting? I thought it save 
automatically, but it didn’t seem to. I pressed the export button - but and 
that seemed to do it, but I wasn’t convinced that is actually save?

Tim

On 8 Aug 2014, at 16:45, Baptiste Quide <baptiste.qu...@inria.fr> wrote:

> Hello,
> 
> i think you select the option "Quit on Launch" (by default) on Pharo 
> Launcher. That's why when you're clicking it just switches to your running 
> image.
> Try to deselect this option and retry.
> 
> Regards,
> 
> ----- Mail original -----
>> De: "Tim Mackinnon" <tim@testit.works>
>> À: "Pharo Users Newsgroup" <pharo-users@lists.pharo.org>
>> Envoyé: Vendredi 8 Août 2014 17:34:06
>> Objet: [Pharo-users] PharoLauncher can only run 1 instance on OSX?
>> 
>> I really like the PharoLauncher project - it’s very handy. However I’ve
>> noticed that on OSX when I launch an image and then try and run
>> PhaorLauncher (e.g. pharo.app) again, it just switches me to my already
>> running image?
>> 
>> Anyone know why it does that - or if there is some way to avoid it? i’m
>> wondering it its the way that the launcher, launches the images (is it an os
>> sub-process or something - and so this is why it just switches back to that
>> process if you try and run it again?).
>> 
>> Tim
>> 
> 


Reply via email to