ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

DonationCoder.com Software > Screenshot Captor

What are these dll files used for?

(1/3) > >>

Huidong:
I have been wondering what CloseApp.dll, CloseApp2.dll, and DcMouseHk.dll are used for. But I did figure out that DcKeyHk.dll is necessary for the shortcut key to work. Could you please tell the function of these dll files? Thank you.

mouser:
Hi Huidong.

the mousehook and keyhook are actually ONLY used in redbox capture mode -- which is optional, and is used to capture regions in windows and menus, and scrolling windows.  they are not loaded until these modes trigger.

closeapp.dll and closeapp2.dll are identical dlls and their only purpose and use is to close an already running version of screenshot captor when the setup installer needs to shut down the application to install an update, or before uninstalling.   The reason there are 2 is that i couldn't find a way to just use 1 with the inno setup installer in both the cases of install and uninstall.

you can see i tried to name them appropriately :)

if you are concerned about them, know that they are all compiled by me personally.  and if you wanted you could delete them, you just wouldn't be able to use red box capture mode in screenshot captor, and you'd have to make sure you manually exited the program from the tray before running update or uninstalling.

Huidong:
Hi mouser,

Thank you for the clarification. I was just curious, not concerned at all. The red-box capture is one of those highlights that make SC outstanding and unique, so I would definitely keep the two hooks. But I will describe by the way some inconvenience with the hook. Using Windows 7, I always run SC with the highest privilege otherwise I guess it can't capture windows associated with elevated processes (correct me if that's not the case). However, this brings a problem when using the two hooks: they do not work when (elevated) SC tries to capture a window associated with a process that's not elevated. Of course a workaround is to click on the gear button to capture, but rather inconvenient. I wonder if there's some fix for this issue?

The other trivial point, I set the capture folder to somewhere, but SC still creates a folder named "Screenshots" in the program directory, I wonder if this can be avoided?

Thank you very much.

Huidong

mouser:
but SC still creates a folder named "Screenshots", I wonder if this can be avoided?
--- End quote ---

hmm that shouldn't happen if it can write into the directory you specify.. ill explore that and the other issue on my windows 7 vmware and see if i can get a clue about it.

Huidong:
By the way, I use SC in portable mode and its directory is not %ProgramFiles%\. Just to be detailed, I start SC with the highest privilege via the following way:

I defined a keyboard shortcut (Win+S) in an AutoHotKey script file, and this script file is run via the Task Scheduler in the highest privilege upon my log-on to the system. Anyway my point is that I do not do "Run as Administrator" (via context menu) to elevate SC.

Navigation

[0] Message Index

[#] Next page

Go to full version