Godot: "Clone to position" shortcut

[ghost]

I think it would be convenient to have the ability to create and place clones of an object with one action. This would be really handy for placing collectibles or other objects all around your scene quickly.

Currently you must select an object in a scene, hit Ctrl-D then drag the cloned item to its position; this shortcut would let you place a clone of the selected object with Ctrl-Shift-click, placing the clone where you've clicked. This would also extend to holding down the click so you could line up the object correctly before placing it.

In practice it would look something like this (taken from GameMaker Studio):

Any discussion or thoughts are welcome.

[HummusSamurai]

Or maybe keep Ctrl + D for cloning, but instead make the position depend on the mouse, like in the shown gif.

[ghost]

I think it would feel more natural to place clones with a click rather than having it be a purely-keyboard shortcut, given that you're using the mouse to set the position. Also, I'd imagine the ability to just clone nodes without changing its position would still be needed in a few cases, so Ctrl-D should probably just keep its current functionality.

[bojidar-bg]

Well, maybe we can get a clone-to-position shortcut (probably defaulting to Shift-Ctrl-D)?

[reduz]

it's not a bad idea, for ctrl-shift-d, but we have the problem of
discoverability, as it's not a shortcut we can put on a menu

On Mon, Jun 26, 2017 at 1:37 PM, novemberist [e-mail]
wrote:

sorry for the nitpicking, but strictly speakiung, duplicating an object
doesn't produce a clone but an independent copy (unless you are duplicating
an instanced scene and make sure changes are applied to all instances of
that scene in your tree). so maybe creating a duplicate or a clone should
be treated/implemented as two seperate things?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/9389#issuecomment-311113500,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z21Je0oUSLr8dg3qAhnSkAFk_cOrwks5sH944gaJpZM4OE058
.

[eon-s]

ok, ctrl+shift for in-place duplication and ctrl for in-cursor :upside_down_face:

[kerskuchen]

This would be awesome as it could be used as node-"paint" tool! There are even plugins like Andreas Esau's Asset Dropper which do a similar (if somewhat more complex) thing. With cursor-node-duplication as @homer666 suggests and a little extra work those kind of plugins would not be needed anymore or extremely simplified.

[kubecz3k]

First of all thank you for your report and sorry for the delay.

We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.

We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about its current status here?

For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

Thanks in advance.

Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

[akien-mga]

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

As there was no update since the previous post, we close this issue.

If it is still relevant in the way it was described and discussed above, please comment to ask for it to be reevaluated. If it is only partly relevant, or if the original issue has changed, it would be better to open a new issue (potentially referring to this one) focused on the current state.