I think that you could just write a Windows application that listens for
WM_DISPLAYCHANGE messages (that are generated when the
ChangeDisplaySettingsEx succeeds) and logs the parameters recieved somewhere
(keep in mind that wParam = new BPP; LOWORD(lParam) = new horizontal
resolution; HIWORD(lParam
On Tue, Mar 4, 2008 at 7:07 PM, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> "Denver Gingerich" <[EMAIL PROTECTED]> wrote:
>
>
> > >gcc -lgdi32 -luser32 -o x x.o -mwindows
> > x.o:x.c:(.text+0x5e): undefined reference to `EnumDisplaySettingsExA'
> > collect2: ld returned 1 exit status
> >
> >
"Denver Gingerich" <[EMAIL PROTECTED]> wrote:
> >gcc -lgdi32 -luser32 -o x x.o -mwindows
> x.o:x.c:(.text+0x5e): undefined reference to `EnumDisplaySettingsExA'
> collect2: ld returned 1 exit status
>
>
> I'm not very familiar with building applications that use the Windows
> API with MinGW so i
On Tue, Mar 4, 2008 at 5:33 PM, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 5. März 2008 01:38:59 schrieb mark cox:
>
> > Perhaps use detours to hook the ChangeDisplaySettingsEx function and dump
> > the devmode structure to a file?
> That's rather complex, a simple C app calling
>
Am Mittwoch, 5. März 2008 01:38:59 schrieb mark cox:
> Perhaps use detours to hook the ChangeDisplaySettingsEx function and dump
> the devmode structure to a file?
That's rather complex, a simple C app calling
EnumDisplaySettingsEx(ENUM_CURRENT_MODE) called from command line should do
that as wel
Perhaps use detours to hook the ChangeDisplaySettingsEx function and dump
the devmode structure to a file?
Regards,
mark
On Wed, Mar 5, 2008 at 9:09 AM, Denver Gingerich <[EMAIL PROTECTED]> wrote:
> I am trying to trace the sequence of screen mode
> (resolution/bpp/refresh rate) changes that occ