Undo does save engine state

Bugs item #1891715, was opened at 2008-02-11 23:28
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=835077&aid=1891715&group_id=165310

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Donald Ephraim Curtis (dcurtis3)
Assigned to: Nobody/Anonymous (nobody)
Summary: Undo does save engine state

Initial Comment:
do the following:

Make an engine only render half of a molecule.

Move an atom in that molecule.

Undo.

Since there is code that is copying a molecule, then the primitives are getting re-added to the engine because the molecule is being copied.

Unfortunatly what we need is some sort of serialization function for our primitive list. Luckily our PrimitiveList class can probably do some sort of thing like this where it saves some data about what atom numbers are being stored. That way the undo function can restore it after copying. This needs work.


You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=835077&aid=1891715&group_id=165310