When cloning features there is a clone(deep) method that also clones the
geometry
Paul
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse01200
Larry,
Thank you for your excellent explanation of undo/redo. This makes a
lot more sense to me now. Basically we only want to support undo/redo
for "edit" operations that change features and their geometries.
Larry wrote: " It seems like you should be able to simply move the
features from one la
> not sure of the consequences of that. I still remember the first time I
> tried to do a copy from one layer to another in code. I ended up with
> two features sharing the same geometry. A potentially useful, but scary
> concept.
ah yes.. i remember that you found this bug as well in my rep
Hi SS,
The undo/redo support is really a java thing that you can support in your
tool, but doesn't really make sense for the toolbar undo and redo buttons.
Those buttons are expected to undo and redo edits, not selections. It also
doesn't normally undo layer operations. For instance you can't
I've been looking at the steps necessary to add undo/redo support to
the Super Select Tool. I had a question or two about memory usage that
someone who has worked with the undo/redo code may be able to help
with.
How is the memory usage of undo/redo handled in OpenJUMP. For example,
will I be hogg
