Hi,
If I get you right you want to make sure that the initial dialog (the one with _cbDialog) don't receive input when the derived dialog is created (_cbDerivedDialog), right?
To achieve that you can simply make the derived dialog modal:
Display All
Regards,
Sven
If I get you right you want to make sure that the initial dialog (the one with _cbDialog) don't receive input when the derived dialog is created (_cbDerivedDialog), right?
To achieve that you can simply make the derived dialog modal:
C Source Code
- static void _cbDerivedDialog(WM_MESSAGE * pMsg) {
- WM_HWIN hItem;
- int NCode;
- int Id;
- WM_KEY_INFO * pInfo = (WM_KEY_INFO *)pMsg->Data.p;
- switch (pMsg->MsgId) {
- case WM_INIT_DIALOG:
- setupDropdown(WM_GetDialogItem(pMsg->hWin, ID_DERIVED_DROPDOWN_0));
- WM_MakeModal(pMsg->hWin);
- break;
- case WM_NOTIFY_PARENT:
- switch (pMsg->Data.v) {
- case WM_NOTIFICATION_RELEASED:
- switch (WM_GetId(pMsg->hWinSrc)) {
- case ID_DERIVED_BUTTON_0:
- GUI_EndDialog(pMsg->hWin, 0);
- isUntouched = 0;
- break;
- }
- break;
- }
- break;
- default:
- WM_DefaultProc(pMsg);
- break;
- }
- }
Sven
Please read the forum rules before posting.
Keep in mind, this is *not* a support forum.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support you can contact us via our support system: segger.com/ticket/
Or you can contact us via e-mail.
Keep in mind, this is *not* a support forum.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support you can contact us via our support system: segger.com/ticket/
Or you can contact us via e-mail.