Undo operation not context based.
Real-Time Event Frameworks based on active objects & state machines
Brought to you by:
quantum-leaps
Menu
▾
▴
#230 Undo operation not context based.
When using Undo shortcut (Ctrl-Z) in code entry window in diagram designer - to undo does not actually act on the code window content but on the graphical content.
How to reproduce:
- Add a state.
- Add 2 signals to the state TRIG1 and TRIG2.
- Click on TRIG1 and add 3 lines of code in the Property Editor for this signal.
- Try to use Ctrl-Z once to undo what you would think is the change you made in you code.
The result is the that TRIG2 signal will dissapear from the diagram. Undo working this way can have a DISASTROUS effects if you have a big diagram and you accidently press Ctrl-Z while working with code, as you are used, to because you expect to work the usual way known from all software IDEs. Pressing it accidently, could for example remove some elements of the diagram or disconnect transitions. Of course the workaround would be to use Redo but it would be very usefull if the Undo could work in more standarized way.
Discussion
Anonymous
+1 to this. Would love context-based undo.
+1 to this - I have been bit several times, and it's difficult to understand which item(s) have been undone. Our fingers are mostly on auto-play, so <ctrl-z> happens before the brain can stop it.</ctrl-z>
Last edit: Dana Good 2020-11-02
+1 The undo is completely broken, as far as I can tell. In only a few days of working with QM, this has made me jump in anger several times (as I also tend to hit ctrl-z faster than my brain can preempt it with the thought of "oh, right, don't use ctrl-z, this GUI doesn't support that").
In the alternative, is there a configuration setting somewhere to disable this shortcut completely? I'm trying to write high integrity code, so I consider having this broken shortcut active as a serious safety hazard.