NO_PROGRAMMATIC_CHANGE_OF_LIBRARY_STATES_PERFORMED becomes semantic data of root state

[franzlst]

This issue was discussed with @sebastian-brunner. The introduced flag NO_PROGRAMMATIC_CHANGE_OF_LIBRARY_STATES_PERFORMED will be removed and substituted by a root state semantic data labeled STATE_IS_DYNAMICALLY_CHANGING.

As long as the for complex state machines (with a lot of different bigger library state machines) it is very helpful to directly use the root state of the first opened library state machine directly in any case as a default behavior. In future it will be aspected that a library root state is semantically annotated if it self or a siblings which is no LibraryState does dynamically change. For the special case the root state semantic data will hold the entry STATE_IS_DYNAMICALLY_CHANGING=True. If the flag is not set it aspected to be set False.

Originally created by @Rbelder at 2018-07-18 10:51:32+00:00 (moved from RMC internal repository)

[franzlst]

If there is a better name to label this kind of library states I am open for feedback. 👍

Originally created by @Rbelder at 2018-07-18 10:53:35+00:00 (moved from RMC internal repository)

[franzlst]

THIS CHANGE SHOULD NOT BE PERFORMED BEFORE INTRODUCING A NEW OVERSEER CLASS which holds one LibraryStateMachine and secures consistency.

Originally created by @Rbelder at 2018-07-18 13:01:11+00:00 (moved from RMC internal repository)

[franzlst]

which holds one LibraryStateMachine ...

i am not exactly sure what you mean, but if the library is still needed it should simply not be deleted!

We should discuss this in our next meeting.

Originally created by @sebastian-brunner ([email protected]) at 2018-07-19 05:40:06+00:00 (moved from RMC internal repository)