Loading AZ presets

[azslow3]

1) all monitors, except of type "Timer Once", are checked on AZ Controller activation. Checked means Logic block containing them is executed in "Monitor checking" mode. And if it comes to Monitor itself (the execution is not abandoned by Action flagged Final and Conditions for Monitor Action itself are ok, it is triggered. In other words, AZ Controller knows when Monitored entity is "undefined". In case of "Context", initial value is "undefined", "NoProject" is a different State and it will be triggered.

You get that monitor triggered (assuming Logic Actions are not preventing that): (1) with "NoProject" (2) "Console"/"Track"/"Plugin" when the project is loaded (2...n) when you change focus between "Console"/"Track"/"Plugin" (n+1) with "NoProject" when you close the project (also in case that is implicit during Sonar exit).

My proposal for "Project" Set is to avoid (2..n) triggers, which will simplify your preset.

(2) everything you set in Logic is executed in "Monitor checking" mode. It is very close to feedback mode, but "Set engine state" flag is working differently from Feedback. All initial states are "real", just changes of them during "Monitor checking" are discarded (after Monitor execution, if triggered, so changes can be "saved" explicitly in Feedback).

Context:NoProject will work correctly during any "Monitor checking". In other words, "Context"  (and all other system states) is  changed by AZ Controller PRIOR executing any "Monitor checking".