DonationCoder.com Software > Screenshot Captor

how to grab and save with the key prt scn

(1/3) > >>

erze26:
hello

i succeeded once to scan the entire screen  and save with only pressing the key prt screen.
but this disapeared.
how can i set it it the program ?

thanks

mouser:
I'm not understanding -- can you elaborate?

erze26:
just pressing the key print screen, i want to capture the sreen and save directly the picture

mouser:
That's how screenshot captor already works :)
Try choosing this option:

IainB:
...i succeeded once to scan the entire screen  and save with only pressing the key prt screen.
but this disapeared.
how can i set it it the program ?
-erze26 (January 23, 2018, 02:07 PM)
--- End quote ---
Despite its being in this thread, I suspect that the OP may not be a ScreenshotCaptor query per se.

@erze26 seems to be talking about the built-in Windows system PrtSc (PrintScreen) function. It does not require a third-party tool such as SC (ScreenshotCaptor) to do that.
The reason the screenshot "disappears" is probably that it just goes to Clipboard as a Copy operation, and is overwritten by the next text or image Copy to Clipboard. Thus, what's in the Clipboard is transient and seems to "disappear". I think the screenshot may also be saved to a default Windows directory, but this will be determined by system settings/preferences.

This is why I keep banging on about CHS (ClipboardHelp & Spell) as being an ideal image capture management tool, if users (and its author) only but realised it. The user can forget about worrying about image filenames or what directory the ruddy image is stored in or where it is.

It really does seem rather like a no-brainer, to me: If CHS is running, then every screenshot image that goes to Clipboard also is saved to the CHS image database folder [NB: together with any post-capture SC(ScreenshotCaptor} artefacts added at time of capture, if SC was being used to make the screenshot], from where the user can, at their leisure, view that image saved - just scroll through the images flagged in the CHS Grid display and view the image (with zooming) in the CHS Memo display. The user can at that point also trigger a separate image viewer (e.g., Irfanview) from the view button in the CHS Memo display, which will have previously been associated with images in the CHS settings. Any half-decent image viewer will also have a built-in image management tool and metadata editing tool. The latter would typically be an EXIF editor - e.g., Irfanview is very good in both regards.

If the user then wants to operate on (edit/change) that image, then they can invoke the third-party image editing tool (e.g., SC is very good) from the edit button in the CHS Memo display and which would have been associated with image editing in the CHS settings. (NB: This would require that SC or other image editor be installed first, of course.)

Done this way, the user:

* can forget about the image file (if/when needed, it's path and name are given in the Text tab in the CHS Memo display), and
* can forget about the viewer/editor applications (they are seamlessly integrated into CHS settings), and
* concentrate on the task at hand - namely the functionality that is required (e.g., image view and/or edit) regarding any particular screen capture or clip or other image selected in CHS.
All the above boils down to making the whole process of image capture management more effective/efficient. It's a useful time-saving approach, simply because it automates the integration of image application functionality. The user typically doesn't generally capture an image because they want to capture it per se, but because they want to do something with the image - or its file -  once it has been captured.

When seeking to improve a frequently-used and manually intensive process, the rule of thumb is generally to automate wherever possible/feasible and cost-effective to do so.
(As usually described in most/any Work Study practitioner's handbook.)
--- End quote ---

Navigation

[0] Message Index

[#] Next page