Thread: [GD-Windows] (no subject)

Brought to you by: vexxed72

gamedevlists-windows

[GD-Windows] (no subject)

From: Doru S. <do...@pc...> - 2003-03-29 21:21:19

Hello and welcome to my first post on this list:

how do you obtain the current color depth? I managed to obtain current =
width and height of the screen using the GetSystemMetrics but I seem to =
have no solution for the BPP.

Can anyone help me?

thx

[GD-Windows] (no subject)

From: Michael A. <man...@ro...> - 2003-04-14 17:53:51

Re: [GD-Windows] (no subject)

From: Brian H. <bri...@py...> - 2003-03-29 21:29:29

Off the top of my head:

HDC hDC =3D GetDC( GetDesktopWindow() );

int bitspixel =3D GetDeviceCaps( hDC, BITSPIXEL );

ReleaseDC( GetDesktopWindow(), hDC );


On Sat, 29 Mar 2003 23:20:37 +0200, Doru Stoenescu wrote:
>Hello and welcome to my first post on this  list:
> 
>how do you obtain the current color depth? I  managed to obtain=
 
current width and height of the screen using the =
 GetSystemMetrics 
but I seem to have no solution for the BPP.
> 
>Can anyone help me?
> 
>thx
>

RE: [GD-Windows] (no subject)

From: Jon W. <hp...@mi...> - 2003-03-30 15:54:46

> HDC hDC =3D GetDC( GetDesktopWindow() );
> int bitspixel =3D GetDeviceCaps( hDC, BITSPIXEL );
> ReleaseDC( GetDesktopWindow(), hDC );


Interesting. I would do it with EnumDisplaySettings passing=20
in something like ENUM_CURRENT_SETTINGS:

  struct foo {
    DEVMODE dm;
    char driversSuck[ 1024 ];
  };
  foo f;
  BOOL b =3D EnumDisplaySettings( NULL, ENUM_CURRENT_SETTINGS, &f.dm );

Look at f.dm.dmPelsWidth, f.dm.dmPelsHeight and f.dm.dmBitsPerPel.

The "driversSuck" field is empirically determined to be necessary=20
on some systems to avoid stack overwrites.

Cheers,

				/ h+

RE: [GD-Windows] (no subject)

From: Brian H. <bri...@py...> - 2003-03-30 17:23:04

>Interesting. I would do it with EnumDisplaySettings passing in
>something like ENUM_CURRENT_SETTINGS:
>
>struct foo { DEVMODE dm; char driversSuck[ 1024 ]; }; foo f;=
 BOOL b
>=3D EnumDisplaySettings( NULL, ENUM_CURRENT_SETTINGS, &f.dm );
>
>Look at f.dm.dmPelsWidth, f.dm.dmPelsHeight and=
 f.dm.dmBitsPerPel.
>
>The "driversSuck" field is empirically determined to be=
 necessary on
>some systems to avoid stack overwrites.

I'm assuming you actually set dm.dmSize =3D sizeof( DEVMODE )?  If=
 not, 
that could cause stuff to explode I would imagine.

Brian

RE: [GD-Windows] (no subject)

From: Jon W. <hp...@mi...> - 2003-03-31 00:14:04

I absolutely set dmSize correctly -- after I memset() the=20
entire structure to 0.

In fact, the constructor for foo calls memset to 0 and=20
then sets dmSize to sizeof( DEVMODE ).

Cheers,

			/ h+