-snip-
> > > The way to do this is:
> > > CreateWindow(...,WS_VISIBLE,0,0,240,320,NULL,NULL,wc.hInstance,NULL);
> > > Don't ask me why! Seems to me a bad idea to do 240,320 hardcoded, but seems
> to
> > > be the only way...
> >
> > This is wrong: You must write (see gapi manual)
> >
> > #define MENU_HEIGHT 26
> > HWND g_hWnd; // Window APP
> > RECT rc;
> > SHFullScreen(g_hWnd, SHFS_HIDESTARTICON | SHFS_HIDETASKBAR |
> > SHFS_HIDESIPBUTTON);
> > GetWindowRect(g_hWnd, &rc);
> > MoveWindow(m_hWnd, rc.left, rc.top-MENU_HEIGHT, rc.right, rc.bottom
> MENU_HEIGHT,
> > TRUE);
> > GXOpenDisplay(g_hWnd, GX_FULLSCREEN);
>
> Thanks for the tip!
> Where's the GAPI manual by the way - I couldn't see one, only examples?
>
> *update* - are you sure about SHFullScreen? I searched for it at MSDN and
> strangely even though it appears in other articles it's not in MSDN itself?
> Seems weird...
>
Thats exactly why I didn't use it either, I had no idea you could.
All the sample apps using Gapi (that I used right after it came out) use the CreateWindow() function.

I'll take a look at it and rewrite it to use that function a soon as I get a chance.

FYI, My first attempt at rewriting this had the full screen blacked out, however it would never refresh the menu bar and clock when I exited MameCE3. I always assumed it was becuase we were blitting to the screen directly and the OS didn't know that we overwrote the menubar. I also couldn't figure out how to tell it that I had written on the menu at the time.
Also, (becuase of this)my blit routine in display.c does not reblit the menubar. It start its blit at the screenframe+=26.

Perhaps we will get a few more frames per second after this change :)


Cheers,
-Techmaster