New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ctrl+C: Copy Screenshot to Clipboard #342
Comments
Do you have any suggestions, that make sense and don't collide with anything else? |
A difficult question.
A customization would be a too big effort for the problem, right? |
I mean I tihnk your concern is totally valid and it's a good idea to change, the question is whether you have a good candidate in mind or somoene is yet to figure that out. PrintScreen itself is handled by OS for desktop capture and also Alt+PrintScreen IIRC. Maybe it should rather be a traditional letter based hotkey, just another one without known conflicts. |
Ctrl+F12 is currently used to save to image file. Maybe use Ctrl+Shift+F12 for clipboard? And add it to the menu as well. |
I will leave #343 for guys to hav a look or otherwise merge in a while (a minor change and makes sense).
They are currently both in menu, one under File, and the other under View. Maybe a bit messy but not that bad. |
I don't think we should just change the short-cut. That could confuse existing users! The more important question is, why is the clipboard command executed on the graph? Does it just bubble up from the the property page or is it never executed on the property page in the first place? |
These might be two related issues, better shortcut & also disablement of scope where accelerators apply. The original request overall looks valid. Repo steps:
|
Currently Ctrl+C copies a screenshot of the graph to the clipboard.
This prevents that a user can use Ctrl+C to copy text from an edit control of a property page to the clipboard.
My biggest wish would be to assign a different key combination to "Copy Screenshot to Clipboard" and avoid standard Windows shortcuts.
Thank you very much in advance.
P.S: GraphStudioNext is great :-)
The text was updated successfully, but these errors were encountered: