Thanks Paul, please inform when the DLLs will be ready, right now these functions are missing
WINDOWATCURSOR# EXPORT_WINDOW_IMAGE LOADRESOURCE
Welcome to our forums
Thanks Paul, please inform when the DLLs will be ready, right now these functions are missing
WINDOWATCURSOR# EXPORT_WINDOW_IMAGE LOADRESOURCE
New DLLs and (in a separate download) new INCLUDE files are available here https://forums.silverfrost.com/Forum/Topic/3780. Only use the downloads for today (April 6 2021).
A revised sample program with resources can be downloaded from https://www.dropbox.com/s/c6azqvjmkczcp8q/capture.zip?dl=0.
p.s. At the moment the sample only works for 64 bits.
I have now updated the downloads for the DLLs and INCLUDE files so that the sample program now works for 32 bits as well as 64 bits.
In the sample program it is necessary to call GetCursorPos@ rather than GetCursorPos. This is the call that was failing for 32 bits.
Paul, The size of saved are is a bit larger than the actual window size. Do you see the same ?
Dan
Yes. I noticed that but I don't know how to easily get the exact size. I have used GetWindowRect and even allowed for the width of the borders. Hopefully it can be tollerated.
Paul, it looks like the shadow of the window is also grabbed. These additional borders always catch some stuff and dirt which also exists on the screen, very annoying and disgusting and for sure requires additional editing to remove them defying the whole purpose of this workaround. So please find the way to kill these borders
Paul,
I was able to test this, and it works very well in the 32 bit environment.
I see what Dan is speaking of, but for assistance in debugging, it is more than sufficient for that purpose.
I wonder what Microsoft does to figure the precise boundaries of the window to do the 'grab'. If I run across anything, I'll let you know!
Again, thanks for the capability!
Bill
Dan
I did have an idea in the night which I will try.
I remember once getting 98% in a maths exam. Since then I try to be satisfied with the 98% even if others aren't.
I put a lot of work into that feature which was a freebe from me to you. If it doesn't suit your purpose then you are free not to use it.
The issue with the borders can be resolved if I call DwmGetWindowAttribute rather than GetWindowRect. At the moment this only works for 64 bits.
This fix will be included in the next release of ClearWin+.
Thanks, Paul!
I will be implementing this newer method in my product regardless of the border display. It is very much faster and less intrusive (system wise) than the simulated Alt+PrntScrn solution for my users.
I will be happy to wait for the 32-bit implementation changes.
Bill
Bill, and as a bonus will sometimes clearly see on the borders what kind of extracurriculum activity goes in the monitors of your customers while they work 😃 😃 😃
And of course kudos to Paul for the trick
This feature is now ready for use and new DLLs are available for download via the sticky post.
Sample code can be downloaded here... https://www.dropbox.com/s/cumk2q12rifif6o/capture.zip?dl=0.
Thanks, Paul!!
Paul, Getting runtime error for missing get_cursor_pos
Dan
Please check that you are using the latest downloads for a) the DLLs and b) the ClearWin+ interfacing. These are dated 9th April and 6th April respectively in the sticky post.
I got all available Apr9 files at that time. Any new additions today?
You will probably also need the latest clearwin.ins etc. donwload dated April 6.
Are you using my latest sample program on this thread?
I used all 6 Apr files. May be Bill will confirm if all works now with no borders?
Dan
Here is a link to download today's DLLs...
https://www.dropbox.com/s/e3qxvqwu27ekeak/newDLLs79.zip?dl=0
And here is a link to download today's clearwin.ins etc...
https://www.dropbox.com/s/uqktplfr55ys33y/clrwin.zip?dl=0.
I don't think that it will make any difference. I am assuming that something when wrong with your earlier downloads.
I can confirm that with these DLL's and INCLUDEs in place, the border is almost entirely removed. There is a tiny sliver on both the bottom and right hand edge. No other edges appear to have any artifacts remaining. Using a special image editor, it would appear that the artifact is only 1 pixel wide.
Bill