Since I originally implemented the PrintScreen key capture functionality in 2008 I can shed some additional light on this subject.
Back then DropBox and OneDrive weren't even around so there wasn't an issue of conflicts.
Second, due to Microsoft's inconsistent key handling in Windows we were forced to "register" an event to detect when the PrintScreen key is actually is pressed. Also due to Microsoft's brain-dead design only 1 program can registers this callback instead of properly chaining to ALL listeners. AppleWin detects if someone else has tried to take control of PrintScreen and will inform the user if it is unable to capture the screen -- since someone else already snagged it first. You can disable this via the command line option:
-no-printscreen-dlg
IMHO the proper solution would be to fallback to a "normal" function key -- along with having a menu option to take a screenshot. I'll have to see what function keys (along with Shift, Control, and Alt. options) are available. This would be a good "wishlist" feature to have down the road.
> Maybe CTRL-PRINTSCREEN or something like that will be fine.
Negative (for now.) Currently Ctrl-PrintScreen copies the text screen (it auto detect 40/80 columns) to the clipboard.
Again, ideally the user should be able to configure the two hotkeys they want to use. As noted, currently this is hard-coded. Having custom hotkeys is another "wishlist" feature to have but this will take some time to do properly.
I've amended Git Bug #380 with these feature requests:
https://github.com/AppleWin/AppleWin/issues/380