Hi,
I can see the advantage in clone and move. I think that this tool is most
useful when digitising and adding new features into that same layer. Replicate
features is clearly made for copying features from one layer into another.
That's also what I have been using it. Perhaps we will want to have them both,
even it is hard to guess the difference between clone and replicate. But mayby
only the Clone tool needs to be on the right click menu and replicate could be
only available from the Edit menu?
Have you developers discovered that both these tools (clone and replicate) seem
to be happy with pasting features also into non-editable layers?
-Jukka Rahkonen-
________________________________
Giuseppe Aruta wrote:
Jukka,
clone items not only duplicate items but also set the copies on editing mode
and opens move-item tool: it allows users to clone and move objects on the
workbench with only one click - the regular duplicate item doesn't have these
capabilities. It has some possible usages, cloning object used for point
simbology or duplicate buildings which have the same shape. I rather use more
this Clone Tool for my maps than the regular Duplicate one - but this is my
point of view, more than this I made that tool.
Regarding your second question, I will try to find a solution. Note that
probabily Replicate Item tool has the same behaviour (I will give a test, too)
Giuseppe
________________________________
Da: Rahkonen Jukka <jukka.rahko...@mmmtike.fi>
A: 'OpenJump develop and use' <jump-pilot-devel@lists.sourceforge.net>
Inviato: Lunedì 23 Gennaio 2012 10:08
Oggetto: [JPP-Devel] Difference between right click Clone items and
replicate-selected-items?
Hi,
There are two tools in the right click menu which seem to almost the same
thing. Clone items does not ask anything, it just clones. Are there other
meaningful differences.
I notices that if I have selected items from many layers the Clone items is
cloning them all into one of the selected layers. It seems to be usually the
layer that is highest on the layer legend but not always. Because the behaviour
is not easy to predict, would it be better to make this tool usable only if
user has exactly one editable layer selected?
-Jukka Rahkonen-
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net<mailto:Jump-pilot-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
