On Wed, 30 Jul 2008, Eric House wrote:
> Before I added a HI_RES_AWARE resource it reported the width as 240.
> Now it reports it as 320. And all of the drawing glitches are gone.
it more a windows-related question rather than cegcc, but as you mention
it: i use HI_RES_AWARE in a .rc file. I
On Wed, Jul 30, 2008 at 11:57:58AM +0200, [EMAIL PROTECTED] wrote:
> When you say "OS is telling me the screen coordinate", how do you get this
> dimensions.
> You may have a problem here ...
I just use GetClientRect();
Before I added a HI_RES_AWARE resource it reported the width as 240.
Now it
> On Tue, 2008-07-29 at 14:19 -0700, Eric House wrote:
> > My app, built with cegcc, is pretty broken on WinMo devices with
> > 320x320 resolution. Turns out the OS is telling me the screen is
> > 240x240, and doing a horrible job of translating between coordinate
> > spaces when drawing.
> >
>
When you say "OS is telling me the screen coordinate", how do you get this
dimensions.
You may have a problem here ...
After I am using a modified class from MSand called screenlib to handle
resizing
On Tue, 29 Jul 2008 14:19:28 -0700, Eric House <[EMAIL PROTECTED]> wrote:
> My app, built with
Hi Eric,
On Tue, 2008-07-29 at 14:19 -0700, Eric House wrote:
> My app, built with cegcc, is pretty broken on WinMo devices with
> 320x320 resolution. Turns out the OS is telling me the screen is
> 240x240, and doing a horrible job of translating between coordinate
> spaces when drawing.
>
mayb
My app, built with cegcc, is pretty broken on WinMo devices with
320x320 resolution. Turns out the OS is telling me the screen is
240x240, and doing a horrible job of translating between coordinate
spaces when drawing.
I don't have access to MS's dev suite to determine if the problem is
limited t
