RE: [Inkscape-devel] Re: Clone command
AFIAR Freehand is using Ctrl-C for clone and Ctrl-D for duplicate.
Ctrl+C does not Copy?! They likely have not read HIG :)
Yes, that is very great. I was very disappointed when I found out that the only difference between Clone and Duplicate in Freehand is that Duplicate moves the duplicated object a bit and Clone does not (or vice versa).
The same was in Corel Draw. IMHO the "duplicate with a shift" is an example of an utterly redundant, "dumbed down" operation - I hope no one will ever come up with a suggestion to implement it in Inkscape :)
BTW Is there a key for making a clone while moving an object (duplicate works with space)?
Not yet, but I thought about enabling space to leave clones, not duplicates. First, this will reduce the file size, and second, clones will be moved in sync with the original, and therefore the chain of clones will behave almost like a stroke. This is not easy to implement, thoough, because currently clones may behave in a rather counterintuitive (although perfectly standard-compliant) ways when the clone is scaled/rotated and the original is then moved, or when both original and clone are selected and moved together. I will try to program special treatment for these situations so they behave more intuitively.
_________________________________________________________________ MSN Premium helps eliminate e-mail viruses. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...
bulia byak wrote:
AFIAR Freehand is using Ctrl-C for clone and Ctrl-D for duplicate.
Ctrl+C does not Copy?! They likely have not read HIG :)
maybe, it was Ctrl-Shift-C and Ctrl-Shift-D, I honestly do not remember, now I am using Inkscape instead and Freehand does not run in Linux/x86 anyway (http://www.codeweavers.com/site/compatibility/browse/name?app_id=121)
BTW Is there a key for making a clone while moving an object (duplicate works with space)?
Not yet, but I thought about enabling space to leave clones, not duplicates.
Yes that would make sense as default, but there should still be a key for producing duplicates instead of clones (like when you want to copy a draft that you want to change in different ways)
[...] and second, clones will be moved in sync with the original, and therefore the chain of clones will behave almost like a stroke.
Is this behavior optional? I could think of many use cases where one only wants the shape to be in sync, not the placement. But maybe a user could put the originals on a special layer that is locked and invisible and thus have the same functionality?
This is not easy to implement, thoough, because currently clones may behave in a rather counterintuitive (although perfectly standard-compliant) ways when the clone is scaled/rotated and the original is then moved, or when both original and clone are selected and moved together. I will try to program special treatment for these situations so they behave more intuitively.
Sounds good. But this is really not that easy.
Regards, Helge
participants (2)
-
bulia byak -
Helge Hielscher