Le 25 janv. 2018 à 14:46, Mariano Martinez Peck <marianopeck@gmail.com> a écrit :
Thanks Christophe,
Is there a way to update my existing Launcher image or should I wait until you release a future binary (no problem, I can wait).
Thanks!
On Thu, Jan 25, 2018 at 10:23 AM, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> wrote:
Le 25 janv. 2018 à 13:54, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> a écrit :
Hi Mariano,
Le 25 janv. 2018 à 12:33, Mariano Martinez Peck <marianopeck@gmail.com <mailto:marianopeck@gmail.com>> a écrit :
Hi Christoph,
One issue I am having is that the Launch without settings is actually running the settings anyway... (it was not the case before).
Do you see this as well?
Hum, yes Iâm able to reproduce that. Could you open a bug entry for this problem (https://github.com/pharo-project/pharo-launcher/issues <https://github.com/pharo-project/pharo-launcher/issues>)? I will take a look at it ASAP.
Was easy to fix:
Name: PharoLauncher-Core-ChristopheDemarey.173 Author: ChristopheDemarey Time: 25 January 2018, 2:22:42.742766 pm UUID: 975f6569-fb1f-0d00-89b5-97830cafd288 Ancestors: PharoLauncher-Core-ChristopheDemarey.172
fixes 2 bugs: - OS detection tu run image for a shell was wrong for OS X - no default preferences option was lost when running image from a shell
The fastest thing for you would be to open Pharo Launcher, then press cmd + p to open monticello browser. Here, just load PharoLauncher-Core-ChristopheDemarey.172 and it will do the job. PharoLauncher bleedingEdge is also available here: http://files.pharo.org/pharo-launcher/bleedingEdge/ but is not always up to date because the build process also build 64-bits images and loading code in 64-bits image fails at least 4 times / 5 tries, so resulting artifacts are not published. I wonder if I should remove 64-bits build for now.