This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
If you delete a class from a class diagram, no undo functionality is provided. If this happens by accident, you have to define the class from scratch. HOW TO REPRODUCE: Deleting a class from the UML diagram. EXPECTED VS. ACTUAL RESULTS: Undo functionality instead creating from scratch.
Also reported in jse forum: http://forum.sun.com/jive/thread.jspa?forumID=174&threadID=107781 Related issue: http://www.netbeans.org/issues/show_bug.cgi?id=78651
*** Issue 118927 has been marked as a duplicate of this issue. ***
So is this in design at the moment? I wasn't 100% sure this is what Peter meant in a comment in the duplicate. I'm just wondering because this is a big deal for being able to use UML in real projects where an accidental change in many elements can have a large impact.
sorry, I was not too clear. I meant the current design is that undo/redo is not yet supported. Yes, I agree that this feature is very important. It's currently on the roadmap for future releases (Promotion J). Below is the link to the UML roadmap. http://wiki.netbeans.org/wiki/view/UMLRoadmap#section-UMLRoadmap-PromotionJ
I don't know how similar the code in UML using graph is to the form module (Matisse) code (both using Swing I suppose...probably only similarities other than an underlying model), but you guys might be able to use the form module undo/redo functionality as a base. Obviously different, but may have something you can use or get ideas from.
It wasn't implemented before because there was direct linage to source code (live roundtrip) and undo/redo was required to store not only diagram changes but also source code changes and fle system changes (classes renaming/deletion, creation etc to correctly restore content of classes, folders), but now it should be easier to implement with less performance hit
*** Issue 123843 has been marked as a duplicate of this issue. ***
*** Issue 123473 has been marked as a duplicate of this issue. ***
The requirement is more general: implement undo/redo functionality for all operations. Without this feature UML support in NB is just for playing around with UML a bit, not even good enough for learning. But if you need to prioritize, my suggestion is, based on consequences of unintended changes: 1) Undo/redo for deletes. 2) Undo/redo for layout. I have been working on a simple deployment diagram and all automatic layout algorithms actually ruined the layout completely. Having no undo capability makes this a really painful experience. Nonetheless UML in NetBeans looks very promising. Sometime in the future NB UML will the only free UML designer, that you can actually use for serious projects. Cheers, Georg
For layout undo there is a workaround: it's possible to save diagram before layout and close without saving after layout to retore state before layout.
*** Issue 136826 has been marked as a duplicate of this issue. ***
*** Issue 152821 has been marked as a duplicate of this issue. ***
*** Issue 153164 has been marked as a duplicate of this issue. ***
*** Issue 154698 has been marked as a duplicate of this issue. ***
*** Issue 135057 has been marked as a duplicate of this issue. ***
Is there any schedule for implementing undo/redo? Will it be available in 7.0? Regards, Georg
sorry, it's currently hard to estimate when it can be done.
Is any work at all being done on UML these days ? Should we just think that UML is unsupported by NetBeans (while a lot of way less important crap - like PHP - is ?)