Using only the tools coming with windows, my workflow was something like this:
- See something interesting
- On Notebook -- find the fucking PRINT SCREEN fn-key-kombination
- Hit PRINT SCREEN with the speed of light
- If possible, open instance of MS Paint
- Save to file
The solution is as easy as it seems -- just have some program sitting in the background which checks whether there's a new picture in the clipboard, and if so, dump it to a file at a defined location. There are two ways of noticing a changed clipboard content -- either polling for whether the contents changed or getting a notification. The notification would need some registering and hooking and passing the notification forward. Compare that to polling, which essentially is having a timer and checking repeatedly whether the hDC for the picture in the clipboard has changed. Facing the decision between timer and integer comparison and some mumbo jumbo API calls (which aren't that big of a deal either, granted; but still some LOC more I can screw up) I sure went for polling.
So in the end, there's this: A little program which -- as soon as a target directory is available -- will check every 10 ms whether the current hDC handle for the picture in the clipboard has changed. If so, dump a copy of the new picture. That's all.
Just a binary: down/cbrdi.exe.zip, Source w/o binary: down/cbrdi-src.zip
SHA256 (cbrdi-src.zip) = 50437a26cd98b6b88bcbba357923bf0573ea9f5d1132b53479b2a403f98ffaf0 SHA256 (cbrdi.exe.zip) = 99a5c9f63048223ffddf1f69c79659faf482d25aceb4adf8751395de2d7ef507 MD5 (cbrdi-src.zip) = 4cdf41aa6487924c7620f0c51557bc14 MD5 (cbrdi.exe.zip) = 938a72e4725828a143919bc21f3724ecNote: I do not recommend the execution of binary files downloaded from the Internet. Read, understand and then compile it yourself. Maybe working with fpc/lazarus, may not.