It is common to map “Ctrl + D” to both the “Duplicate” action for instances in the Explorer window as well as the “Select next occurrence” action when doing multi-cursor selection in a script editor window.
[Bug Issue]
If you have a selection in the Explorer and you start editing in code, your “Ctrl + D” actions in the script editor will end up bleeding into the Explorer and unintentionally duplicate a ton of objects.
This behavior does not happen every time and can be inconsistent to reproduce. It also seems to mostly happen when you pop the Script Editor into its own widget.
Immediately start pressing “Ctrl + D” in the script editor to select code
Watch how the explorer selection from opening the script ends up duplicating the script repeatedly (this may not always happen, if it doesn’t, then close the script, reopen it and try again)
[Video repro]
Expected behavior
If this were working properly, we should never have to worry about script instances accidentally duplicating themselves (or any other action for that matter) while you are focused into the Script Editor window and making all sorts of key inputs that may be interpreted differently outside of it.
Hi - thanks for the report and updated video. It doesn’t happen everytime for me, but I have been able to reproduce the issue as described often enough. We believe we’ve identified the root cause of the problem and are working on a solution. I’ll reply back to this topic once the fix is available in a Studio update. Thanks.
Hi - the latest fix is live on Studio. At your convenience, please Update Studio and verify in the About box that you’re running version 0.692.X.YZ . Please let me know if you are still experiencing the issue. Thanks.
@litozinnamon The latest release of Studio should have the fix for this. That just came out, I’m rolling it out now. I’ll post back here once it’s available for you to restart and try again. Thanks.
@1987rab Seems like it is fixed so far, my attempts to reproduce it have stopped showing up.
I’ll post any new findings if I run into the issue again somehow, but otherwise I believe this is good to go.