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