When I took the latest 50 Pharo5.0 Latest update: #50152 I get a Halt. DoIt ^ StartupPreferencesLoader default executeAtomicItems: {StartupAction name: 'Self halt' code: [ self halt ]. StartupAction name: 'WS' code: [ Workspace open ]} I wonder if I did something special to activate it. Stef
Le 04/07/2015 23:29, stepharo a écrit :
When I took the latest 50 Pharo5.0 Latest update: #50152
I get a Halt.
DoIt ^ StartupPreferencesLoader default executeAtomicItems: {StartupAction name: 'Self halt' code: [ self halt ]. StartupAction name: 'WS' code: [ Workspace open ]}
I wonder if I did something special to activate it.
I have no problem at statup with the version 50152.
Stef
thank cyril I saw that and I have not idea why one I execute this example3 method now I get the startup of fresh image. I would really like to get startUppreference to be loaded on demand. Stef Le 4/7/15 23:55, Ferlicot D. Cyril a écrit :
Le 04/07/2015 23:29, stepharo a écrit :
When I took the latest 50 Pharo5.0 Latest update: #50152
I get a Halt.
DoIt ^ StartupPreferencesLoader default executeAtomicItems: {StartupAction name: 'Self halt' code: [ self halt ]. StartupAction name: 'WS' code: [ Workspace open ]}
I wonder if I did something special to activate it.
I have no problem at statup with the version 50152.
Stef
Le 05/07/2015 12:44, stepharo a écrit :
thank cyril I saw that and I have not idea why one I execute this example3 method now I get the startup of fresh image. I would really like to get startUppreference to be loaded on demand.
Stef
+1 for this. Sometimes I want an image without startup preferences when I have to take some screen for example without the dark theme. I know there is a way to disable the startup preference with command lines, we do it with one of the Pillar's build but we should not have to do that. ./pharo Pharo.image eval --save "StartupPreferencesLoader allowStartupScript: false."
participants (2)
-
Ferlicot D. Cyril -
stepharo