21 Mar
2016
21 Mar
'16
3:03 p.m.
Le 21 mars 2016 à 14:49, Yuriy Tymchuk
<yuriy.tymchuk(a)me.com> a écrit :
Are you sure that not depending on the other startup items is ok?
We had a discussion there on this point:
https://pharo.fogbugz.com/f/cases/17834/World-Morph-is-started-up-before-Fo…
Because My code definitely has to run after setting
are loaded, so I’ve put it on default + 1000 priority. Now if the preferences priority
will be moved, I have to also my my startup actions. To avoid doing this manually I think
I will simply lookup that priority of SystemSettingsPersistence and add something to it,
so my action will run later. This defeats the purpose of the startup changes.
It looked good but there could be other use cases like yours.
I think the best would be to execute startup of system preferences just before the user
category.
This way, you could register QA in the user category without checking system preferences
order.