Some windows needs to create a full-screen child window (in my case, a keypad). However the parent window isn't full-screen, so the keypad will not be full-screen too.
I know I can create the keypad window as a child of the background window (and put it at the top), however in this case the keypad will not be automatically deleted when the creator window is deleted.
Is there a better approach? Is it possible to create a child window larger than the parent window?
Hi,
you could create the fullscreen window as child of the WM_HBKWIN (the desktop window) and remember its handle. Once the smaller 'parent'-window gets deleted you also delete the fullscreen child.
Like this:
#include "DIALOG.h"
/*********************************************************************
*
* Externals
*
**********************************************************************
*/
/*********************************************************************
*
* Defines
*
**********************************************************************
*/
/*********************************************************************
*
* Static data
*
**********************************************************************
*/
/*********************************************************************
*
* Static code
*
**********************************************************************
*/
/*********************************************************************
*
* _cbFullScreen
*/
static void _cbFullScreen(WM_MESSAGE * pMsg) {
switch (pMsg->MsgId) {
case WM_PAINT:
GUI_SetBkColor(GUI_GREEN);
GUI_Clear();
GUI_DispString("FullScreen");
break;
default:
WM_DefaultProc(pMsg);
break;
}
}
/*********************************************************************
*
* _cbParent
*/
static void _cbParent(WM_MESSAGE * pMsg) {
static WM_HWIN hFullscreen;
static int Once;
switch (pMsg->MsgId) {
case WM_CREATE:
WM_CreateTimer(pMsg->hWin, 0, 1000, 0);
break;
case WM_TIMER:
if (hFullscreen == 0) {
hFullscreen = WM_CreateWindowAsChild(0, 0, LCD_GetXSize(), LCD_GetYSize(), WM_HBKWIN, WM_CF_SHOW, _cbFullScreen, 0);
}
if (Once) {
WM_DeleteWindow(pMsg->hWin);
} else {
WM_RestartTimer((WM_HTIMER)pMsg->Data.v, 0);
}
Once = 1;
break;
case WM_PAINT:
GUI_SetBkColor(GUI_RED);
GUI_Clear();
GUI_DispString("Parent");
break;
case WM_DELETE:
if (hFullscreen) {
WM_DeleteWindow(hFullscreen);
hFullscreen = 0;
}
break;
default:
WM_DefaultProc(pMsg);
break;
}
}
/*********************************************************************
*
* _cbBk
*/
static void _cbBk(WM_MESSAGE * pMsg) {
switch (pMsg->MsgId) {
case WM_PAINT:
GUI_SetBkColor(GUI_BLACK);
GUI_Clear();
break;
default:
WM_DefaultProc(pMsg);
break;
}
}
/*********************************************************************
*
* Public code
*
**********************************************************************
*/
/*********************************************************************
*
* MainTask
*/
void MainTask(void) {
GUI_Init();
WM_SetCallback(WM_HBKWIN, _cbBk);
WM_CreateWindowAsChild(50, 50, 100, 100, WM_HBKWIN, WM_CF_SHOW, _cbParent, 0);
while (1) {
GUI_Delay(100);
}
}
/*************************** End of file ****************************/Regards,
Sven
I noticed you use 0 to invalidate the handle. I usually use WM_HWIN_NULL for this, even if it is really 0.
I suppose a valid handle can't be never 0. Is it correct?
Don’t have an account yet? Register yourself now and be a part of our community!