Ctrl + C to Copy Stops Working
Hello team,
I have an intermittent issue, and have noticed other users experiencing it too, where using Ctrl + C stops working, and instead it just write s a 'C' in the object you're trying to copy.
I've not figured out anything that appears to trigger it, or what makes it start working again. But suffice to say it can be very disruptive. :)
Would love to know if I've accidentally pushed a key/button I shouldn't have or if it's some sort of bug.
Best Answer
-
Hi @PragmaticShift,
To report a bug, please contact [email protected] and include the following information:
Steps that you are taking while encountering the bug, a screen recording or screenshots if possible, your workspace ID, the browser you are using, and your operating system.
I recommend also trying this out on different browsers (Chrome, Firefox, Safari or Edge) based on your operating system to see if this is consistently happening no matter what browser you're using. If you find that it's still occurring, as mentioned, please do reach out MURAL Support at [email protected] for more assistance.
0
Answers
-
Hi @PragmaticShift!
Although I'm not too sure how to fix your bug with Ctrl + C, I do know that you can duplicate objects using the Option/Alt key. All you have to do is:
1. Select the object that you would like to duplicate.
2: Hold the Option/Alt key, click on the object, and drag it out into an empty space.
When you release the mouse, a copy of the object should have been created without losing the original object!
0 -
@PragmaticShift, checking on this one- still happening for you? Let me know if this one's still an issue 😉
0 -
Sorry for the super late reply. But yes, it still happens intermittently. Still haven't figured out what seems to be causing it I'm afraid.
0 -
Thanks, @PragmaticShift. Could you follow the steps above recommended by Support? @Nikki, could you keep watch for this and see if we can help?
0 -
Hi! I'm glad I found this Question. This issue has been driving us crazy over here for several months.
Just FYI: The workaround recommended by Support worked for me.
2 -
Awesome! Glad to hear, @juanmello!
0