Warning when destroying the class mutation history

[Vladimir_Drzik]

Let's have the following standard situation:

It happens quite often that you accidentally start dragging the class in the project window and sometimes you drop it outside of the containing lvlib. Now if you don't realize what has just happened, you drag-and-drop the class back inside the lvlib and save everything. Which means you've just lost the mutation history data and cannot load your persistent data any more. This is extremely dangerous (unless you have a quite fresh backup of your class).

I suggest that a serious warning message is popped up every time a class mutation history is about to be destroyed.

[Nitrof]

I should be forbidden to hide such operation to the developers.

User should have a clear view of what is happening to mutation history.

I suggest that a serious warning message is popped up every time a class mutation history is about to be destroyed/modified/...  Every events concerning mutation.

[AristosQueue (NI)]

I'll leave the idea open, but when this has been proposed in the past, there has been a lot of resistance. Popping up warning dialogs on all these common operations made people feel that the mutation history lost all of its value of being "just something that automatically gets taken care of while I work". The idea mentioned a "serious" warning message. The other big problem with any serious warning is that automutation is covering a problem most people don't even realize that they have. Any sort of serious warning for perfectly reasonable editing operations generates fear and confusion among users who don't quite know about the feature even existing. That's part of the value that would be lost.

I understand the concern, and share it, although it does rarely come up on the forums. I'm just not sure that warnings are the right approach. Better might be to add Undo to the project tree, for example. Or maybe warnings are the right approach, but not as something that interrupts your work but just as something that sits in the corner and says "this happened" so you know not to save changes. There are lots of possibilities here. Might be worth talking through which approach would most preserve the value of automutation while hedging against mistakes.

[Daklu]

I second AQ's thoughts.  Warning dialogs for common operations are annoying.  I'd much rather have an undo feature in the project tree.

(I also really like the idea of a console window listing all the things LV does in the background and think it would be more broadly useful, if a bit overkill for this particular issue.)