heroes of might 2 and magic download

Name: heroes of might 2 and magic download
Category: Free
Published: taconxiga1974
Language: English

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

note: Basicaly I need to know where my window is visible, so I can have the precise region data on another comuter.
this is the idea, but you need to adapt the code for your own need.
Edited by Ivan Zivkovic 86 Saturday, November 2, 2013 9:12 PM.
well the answer is this- major workaround : to get the visible region data, you need to test many points aboive your window X,Y coordinates to see if they are visible (first in the Z axis), simple for loop will do, but for each X,Y point you will need to call WindowFromPoint(POINT input_point), and then to test if the window handle above that specific point is equal to your window handle.

So GetRegionData is working when I create some complicated region manualy, but it fails to calculate the visible regions of a window that is overlapped with some other window.
All replies.
I understand that desktop composition basically sends a buffer of all windows to the Graphic card. and that graphic card calculates which window to draw. I guess by Z-order.
Getregiondata example download.
I had to return after year and a half to put down the answer. that i found then.
Is there a way to calculate visible regions of a selected window while Desktop Composition is on ?
I am using WinGDI Function GetRegionData to calculate visible regions of a window, so that I know by that region information where to draw another window. But, in Windows 7 with Desktop Composition and with Windows 8 ,where Desktop Composition is turn on by default, by call to GetRegionData does not detect regions correctly. It just detects one rectangle, and does not calculate correctly when for example i put notepad over the whole window, its still detects one region. I do not have this problem when I shut down Desktop Composition in Win7.
If it is not equal it means another windows is above your window, then you need to get the region data of the both the window that is above, and your own window, which is realy easy to do, using GetRegionData wich will return the complete area of both windows (causing the need for this workaround), but now as you have both visible regions, you can use CombineRgn(. ) WinAPI funciton to delete the fisible regions from your own region data, thus knowing what part of your window is not visible. Repeating this for other windows that are above yours in the Z axis. Your do not really have to do this for every pixel.
http://takutugu1980.eklablog.com/download-busybox-installer-a177945320