Windows API

你好 (Hello) You have to post in the EasyHook page comments here[^] (at end of article).

Nobody is answering because in the other thread you have been requested to reformat your code to make it readable, but you stll left it as is also here...

Please don't post in multiple places. PCI driver Development[^]

Thanks for reply. "Years ago" I have only to deal with visibility. With the mouse you can click them all. But today people like to foul the screen with their fingers. It seems that the API GetDeviceCaps did not work right with the new Windows Display Driver Model (WDDM) beginning with Windows Vista. I found out a way to get the screen driver info from registry but that don't work for old XP. I hope OS gets an upgrade to better support touchable objects for native desktop applications.

Please do not post the same question in multiple forums.

Thanks, Jochen. This did the trick.

Thank you! I'm trying to map this to C#. I thought I could get a generic answer in the Windows API forum first before I try with C#. /Steffe

I read this and it was extremely helpful. I can use things like: \\?\PhysicalDrive0 \\?\CDRom0 to get the number of partitions on the devices I can use: \\?\GLOBALROOT\Device\Harddisk0\Partition0 \\?\GLOBALROOT\Device\CDRom0\Partition0 to get handles to the various partitions on fixed and removable drives but not on cdroms Any suggestions on how to get partition info for cd drives? Thanks MRM

SMD111 wrote: C is a low-level language that shows how things exactly work For the things you write, yes. It does not show the internals of the WinAPI, and you can call those functions from higher level languages. If there are policies playing along (or other settings or stuff like a corrupted register), then the problem should re-occur in whatever language you use to call the API. SMD111 wrote: This is a Windows API forum, right? It looks like we are speaking different languages ;) I assumed English, my bad. Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

Charles Petzold's book was a bible for low level C WinAPI for quite a long time - and still applies today. It isn't geared towards Windows 8 - but will get you up and running... http://www.charlespetzold.com/pw5/[^]

Ok, too bad. Thanks anyway.

I am afraiod you are doing it the wrong way. All actions in Windows are driven by messages received in the application (or thread) message pump. When a WM_PAINT message is received it indicates that the Window in question requires repainting. If you do your window painting in some other function and ignore the WM_PAINT messages then you will get the result that you see.

You could speed up your program by not reading the pixel on every mouse position change. You could call that part of the code if the mouse has been hovering over a pixel for a while e.g. 500 ms or 1000 ms. Cheers! "I had the right to remain silent, but I didn't have the ability!" Ron White, Comedian

It is explained in the documentation[^].