And what if you have several first actions? On 9 February 2015 at 12:44, Roberto Minelli <roberto.minelli@usi.ch> wrote:
Nope. Imagine (and this is my case) that I distribute a startup script to my users and I want, on them machine, that my script runs last. How can you achieve that?
However, I believe that we need a mechanism for that and not workarounds ;)
R
On 09 Feb 2015, at 12:16, Guillermo Polito <guillermopolito@gmail.com> wrote:
Can't you as a workaround use only one startup action that performs both actions sequentially?
StartupPreferencesLoader default executeAtomicItems: { StartupAction name: âMy second startup actionâ code: [ "the code of the *first* startup action"
"the code of the *second* startup action" ] runOnce: true }
El Mon Feb 09 2015 at 12:07:04 PM, Roberto Minelli <roberto.minelli@usi.ch> escribió:
Hi,
I already asked this question a while ago, and Iâd love to know if something has changed: Is there any way to specify an order or priority of StartupAction?
In my case, for example, I really need that one of my scripts gets executed last. Can I do that?
I could imagine something like
StartupPreferencesLoader default executeAtomicItems: { StartupAction name: âMy first startup actionâ code: [ âSome code here" ] * order: 1* runOnce: true }
StartupPreferencesLoader default executeAtomicItems: { StartupAction name: âMy second startup actionâ code: [ âSome code here that gets executed after the code in My first startup actionâ ] * order: 2* runOnce: true }
On top of my knowledge, after checking 'Deep into Pharo' and âPharo for the Enterpriseâ, it seems that this is not possible.
Am I the only one needing this? I can also try to sketch a solution!
Cheers, Roby
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet