EnumDisplayMonitors API will give you details.
I've used code from http://vbnet.mvps.org/index.html?code/screen/index.html to manipulate monitor properties.
HTH,
Scott
We have an application that automatically detects the number of monitors and the screen sizes when it launches, and then it will automatically fill the screen on the pc appropriately based on what it detects in Windows. You can NOT manually size the window of this application.
However the problem is that we have blade pcs, with special video cards for multiple monitors that we want to run this application on. On these blade pcs, windows only thinks there is 1 monitor, because it is the nvidia driver that is handling the multiple monitor display rather than windows on these particular pcs. This results in the application stretching across both monitors as if they were one large monitor which is not what should happen if the application properly detects 2 monitors. We are working with the application vendor to determine what exactly they are reading from in windows (API, reg key, ini file, etc) to detect the number of monitors but have not heard back. We are also working with the hardware manufacturer to try and come up with a solution but also have had no luck there.
My question is this: does anybody know more specifically where in windows an application might read the number of monitors or the size of the screen? (API, reg key, ini file, etc) All we have been told is "We check windows" and that is not really helping at this point. I also know where to check in windows by opening up the display properties, but I am more interested in how applications might read and return this information rather than how a user interacts with it. If I know this answer we might be able to come up with a solution to our issue.
Thank You,
_______________________________________________ *Jon Luchette *** *Emerson Hospital* *Technology Specialist III* *Work: 978-287-3369* *Cell: 978-360-1379*
jluchette@xxxxxxxxxxxxxxx *_______________________________________________*
--
Thanks, Scott D.