Skip to content
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

[Windows] Global shortcut interference #514

fuzzyweapon opened this issue Jul 30, 2020 · 1 comment

[Windows] Global shortcut interference #514

fuzzyweapon opened this issue Jul 30, 2020 · 1 comment


Copy link

@fuzzyweapon fuzzyweapon commented Jul 30, 2020

So I use Greenshot (I just started using it on Windows recently though) to take screenshots. It's a pretty popular program for that purpose.

Greenshot intercepts standard prtsc keybindings to activate a region selection screenshot tool. This has worked 100% of the time in all apps until I ran into Potato.

When Potato has focus, it is still being used as the native functionality. I do not have prtsc bound to anything in Potato. Could this be because of the way Potato deals with shortcuts itself? Note, I have made sure that Potato does not have any auxiliary windows up or anything (world settings, etc), to isolate possible extraneous variables.

Greenshot compatibility might be niche, but the broader concern might be that this would affect other applications' keybindings that are not bound in Potato because Potato isn't falling back. I haven't tested this and have no idea if "fixing" this would make Potato bindings impossible, so take this all with a grain of salt.

My use case:
I confess that I like sharing poses and mush ascii art via screenshot bc they are often easier to see this way, but I'm not really into showing people all of the worlds and alts I have open. My alternative is to use the alt+prtsc (capture window) functionality and then edit every single screenshot to crop out my other mushes and characters (connections) before dropping it in Discord/etc which kind of makes the idea of impromptu shares tedious and moot.

Copy link

@talvo talvo commented Aug 6, 2020

The short answer to this one, I'm afraid, is that I don't know. I'm not sure quite how Tk handles keyboard bindings under the hood, but actually now that I look, I can't see that Tk actually handles custom bindings for the PrintScreen key anyway.

In terms of actually fixing the problem, the best I can offer would be that you could raise this as a possible bug/issue on the Tcl/Tk bug tracker and see if someone with knowledge of Tk's internals can comment.

In terms of your specific use-case, I can help you with some custom code that'll capture the output screen into an image file, if that's helpful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants