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
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
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.quide@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
Tim Mackinnon wrote:
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
I had this behaviour on Mavericks, and after a while I was going to report it, but a few days ago I noticed that it suddenly went away, and now could launch multiple images and open PharoLauncher again each time. When I noticed this, it had been a few days since anything changed, so I can't pin down what that might be. Maybe I downloaded a newer VM from files.pharo.org, or maybe I re-installed PharoLauncher with a later version, or maybe an OSX update. My PharoLauncher's current system details are: * Image: #30848 . * VM: Mac Cocoa Cog 5.8b12 21-Sep-10 NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 May 15 2014 NBCogit NativeBoostCogPlugin-GuillermoPolito.19 May 15 2014. cheers -ben
Thanks Ben - you are right, there has been another release since I downloaded it (might have to look at how to detect a version update in the launcher to spot that - that would keep me busy ;) Iâm fixed now. Tim On 9 Aug 2014, at 06:29, Ben Coman <btc@openInWorld.com> wrote:
Tim Mackinnon wrote:
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
I had this behaviour on Mavericks, and after a while I was going to report it, but a few days ago I noticed that it suddenly went away, and now could launch multiple images and open PharoLauncher again each time. When I noticed this, it had been a few days since anything changed, so I can't pin down what that might be. Maybe I downloaded a newer VM from files.pharo.org, or maybe I re-installed PharoLauncher with a later version, or maybe an OSX update. My PharoLauncher's current system details are: * Image: #30848 . * VM: Mac Cocoa Cog 5.8b12 21-Sep-10 NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 May 15 2014 NBCogit NativeBoostCogPlugin-GuillermoPolito.19 May 15 2014.
cheers -ben
Actually Ben - I take it back, it still seems to want to only launch a single instance with v.3.0.0 - Iâm not sure whatâs going on (and when iâm back at the office I will have to check it with my desktop version as swear it was working properly). Tim On 9 Aug 2014, at 13:20, Tim Mackinnon <tim@testit.works> wrote:
Thanks Ben - you are right, there has been another release since I downloaded it (might have to look at how to detect a version update in the launcher to spot that - that would keep me busy ;)
Iâm fixed now.
Tim
On 9 Aug 2014, at 06:29, Ben Coman <btc@openInWorld.com> wrote:
Tim Mackinnon wrote:
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
I had this behaviour on Mavericks, and after a while I was going to report it, but a few days ago I noticed that it suddenly went away, and now could launch multiple images and open PharoLauncher again each time. When I noticed this, it had been a few days since anything changed, so I can't pin down what that might be. Maybe I downloaded a newer VM from files.pharo.org, or maybe I re-installed PharoLauncher with a later version, or maybe an OSX update. My PharoLauncher's current system details are: * Image: #30848 . * VM: Mac Cocoa Cog 5.8b12 21-Sep-10 NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 May 15 2014 NBCogit NativeBoostCogPlugin-GuillermoPolito.19 May 15 2014.
cheers -ben
participants (3)
-
Baptiste Quide -
Ben Coman -
Tim Mackinnon