Context Navigation

Changes between Initial Version and Version 1 of Ticket #3488, comment 8

initial	v1
10	10	In fact, there are some cases where it would make sense that the user's flags override the library's, and some where it is the other way round. It depends on whether the expert user is writing the library or playing around with omc flags.
11	11
12		If it is easier to implement a scheme where the annotation wins, that's perfectly fine for me. In that case, I would only recommend to add two flags {{{--ignoreCommandLineOptionsAnnotation}}} and {{{-ignoreSimulationFlagsAnnotation}}}, so that an expert user can always override the library settings (which will simply be ignored) without the need to change the library source code. Of course in that case one has to explicitly apply all the annnotation-set flags which makes sense, but this is crystal clear and trivial to implement for any expert user.
	12	If it is easier to implement a scheme where the annotation wins, that's perfectly fine for me. In that case, I would only recommend to add two flags {{{--ignoreCommandLineOptionsAnnotation}}} and {{{-ignoreSimulationFlagsAnnotation}}}, so that an expert user can always override the library settings (which will simply be ignored) without the need to change the library source code. Of course in that case one has to explicitly apply all the annnotation-set flags which make sense, but this is crystal clear and trivial to implement for any expert user.
13	13
14	14	Would this be ok?