🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:41c07e5c$1@newsgroups.borland.com...
> > when I go to call ChangeDisplaySettingsEx I get an access violation.
>
> Please show your actual code.  An AV is caused by accessing invalid
memory.

8-)

OK, I've corrected a big DOH in the initialisation of my app, and I'm no
longer getting the AV. The original problem remains, though; no 'detaching'
of the monitor. MSDN states "To detach the monitor, set DEVMODE.dmFields to
DM_POSITION but set DEVMODE.dmPelsWidth and DEVMODE.dmPelsHeight to zero.",
but that's not what I'm getting. Here's the code:

   DEVMODE dm;
   dm.dmSize = sizeof(DEVMODE);

   if (0 != EnumDisplaySettings(FMonitorInfo.DeviceName,
                                ENUM_CURRENT_SETTINGS,
                                &dm))
   {
      dm.dmFields       = DM_POSITION;
      dm.dmPelsWidth    = 0;
      dm.dmPelsHeight   = 0;

      LONG lResult = ChangeDisplaySettingsEx(FMonitorInfo.szDevice,
                                             &dm,
                                             NULL,
                                             0,
                                             NULL);
    ...

and lResult is coming back as DISP_CHANGE_SUCCESSFUL. But, the monitor is
still at the same position and certainly not 'detached'. (BTW, FMonitorInfo
is a copy of the DISPLAY_DEVICE result of an earlier call to
EnumDisplayDevices for the monitor.)

Thanks again for any advice...