QM 3.1.3 choice - guard: not not fully displayed and blanks removed
Real-Time Event Frameworks based on active objects & state machines
Brought to you by:
quantum-leaps
Menu
▾
▴
#98 QM 3.1.3 choice - guard: not not fully displayed and blanks removed
Upgraded from QM 2.3.2 to QM 3.1.3. I use the guard: entry for a choice to document the transition (e.g., "More packets to send"). In 3.1.3 the field is truncated to 13 characters with a trailing ~ and spaces are removed in the GUI display (e.g., "More packetto~".
Discussion
Anonymous
This is not a bug, but an intended feature in QM 3.1.3. This version uses the user-given names to model items in the generated comments in the code. These comments are then useful to navigate between the model and the code (by copy and paste).
I hope you understand that very long names are not good for this.
Advice: use shorter abbreviations of your guards.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
My preference would be to see the un-abbreviated guard condition on the QM display. The problem is worse if the guard name is left empty and QM shows the abbreviated guard code. Finding corresponding code text has never been an issue for me, but squeezing a meaningful description of a guard down to 14 characters is rather inconvenient. For example, "CPU_TEMPERATUR~" which I tried to use when I noticed that the guard code "ID(e) == CPU_TEMPERATURE" had been mangled.
Fixed in QM 4.x.
--MMS