WM_SetUntouchable() - issue with this new function from v.5.50

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • WM_SetUntouchable() - issue with this new function from v.5.50

      Hello.

      I found the issue with the function WM_SetUntouchable.

      Conditions:

      1. There is a window bottomWin, it contains the button, that creates new window newWin, which fully overlaps bottomWin.

      2. newWin contains a button that creates two new small derWin_1 and derWin_2.
      After creating of them the newWin should be untouchable until windows derWin_1 and derWin_2 will be closed.
      The windows derWin_1 and derWin_2 both should can receive PID-events:
      - one of them is the window (derWin_1) with some editable widgets like EDIT, SPINBOX etc., that should receive keys from virtual keyboard,
      - second is the virtual keyboard (derWin_2).

      I used the function WM_SetUntouchable for making the newWin untouchable.

      Issue:
      If I touch on the area of the untouchable newWin then this touch reaches the touchable bottomWin, it appears on top over all windows with focus on it.

      Question:
      Is this behaviour correct considering the newWin fully overlaps the bottomWin?

      C Source Code

      1. #include "DIALOG.h"
      3. static WM_HWIN bottomWin;
      4. static WM_HWIN newWin;
      5. static WM_HWIN derWin_1;
      6. static WM_HWIN derWin_2;
      8. static const GUI_WIDGET_CREATE_INFO _aBottom[] = {
      9. { FRAMEWIN_CreateIndirect, "Main window", 0, 0, 0, 200, 200, FRAMEWIN_CF_MOVEABLE, 0x0, 0 },
      10. { BUTTON_CreateIndirect, "New window", GUI_ID_BUTTON0, 50, 50, 80, 20, 0, 0x0, 0 },
      11. };
      13. static const GUI_WIDGET_CREATE_INFO _aNew[] = {
      14. { FRAMEWIN_CreateIndirect, "New window", 0, 0, 0, 200, 200, FRAMEWIN_CF_MOVEABLE, 0x0, 0 },
      15. { BUTTON_CreateIndirect, "Two windows", GUI_ID_BUTTON0, 40, 40, 80, 20, 0, 0x0, 0 },
      16. { BUTTON_CreateIndirect, "Close", GUI_ID_BUTTON1, 40, 80, 80, 20, 0, 0x0, 0 },
      17. };
      19. static const GUI_WIDGET_CREATE_INFO _aDer_1[] = {
      20. { FRAMEWIN_CreateIndirect, "Derived window 1", NULL, 100, 10, 150, 90, FRAMEWIN_CF_MOVEABLE, 0x0, 0 },
      21. { MULTIEDIT_CreateIndirect, NULL, GUI_ID_EDIT0, 10, 10, 80, 50, 0, 0x128, 128 },
      22. };
      24. static const GUI_WIDGET_CREATE_INFO _aDer_2[] = {
      25. { FRAMEWIN_CreateIndirect, "Small kbd", NULL, 100, 120, 150, 90, FRAMEWIN_CF_MOVEABLE, 0x0, 0 },
      26. { BUTTON_CreateIndirect, "0", GUI_ID_BUTTON0, 10, 10, 20, 20, 0, 0x0, 0 },
      27. { BUTTON_CreateIndirect, "1", GUI_ID_BUTTON1, 40, 10, 20, 20, 0, 0x0, 0 },
      28. { BUTTON_CreateIndirect, "2", GUI_ID_BUTTON2, 70, 10, 20, 20, 0, 0x0, 0 },
      29. { BUTTON_CreateIndirect, "3", GUI_ID_BUTTON3, 100, 10, 20, 20, 0, 0x0, 0 },
      30. { BUTTON_CreateIndirect, "Close", GUI_ID_BUTTON9, 10, 40, 80, 20, 0, 0x0, 0 },
      31. };
      33. static void _cbDer_2(WM_MESSAGE * pMsg) {
      34. int NCode;
      36. switch (pMsg->MsgId) {
      38. case WM_INIT_DIALOG:
      39. BUTTON_SetFocusable(WM_GetDialogItem(pMsg->hWin, GUI_ID_BUTTON0), 0);
      40. BUTTON_SetFocusable(WM_GetDialogItem(pMsg->hWin, GUI_ID_BUTTON1), 0);
      41. BUTTON_SetFocusable(WM_GetDialogItem(pMsg->hWin, GUI_ID_BUTTON2), 0);
      42. BUTTON_SetFocusable(WM_GetDialogItem(pMsg->hWin, GUI_ID_BUTTON3), 0);
      43. break;
      45. case WM_NOTIFY_PARENT:
      46. switch (pMsg->Data.v) {
      48. case WM_NOTIFICATION_RELEASED:
      49. switch (WM_GetId(pMsg->hWinSrc)) {
      51. case GUI_ID_BUTTON0 ... GUI_ID_BUTTON8:
      52. NCode = 0;
      53. BUTTON_GetText(pMsg->hWinSrc, &NCode, 2);
      54. GUI_SendKeyMsg(NCode, 1);
      55. break;
      57. case GUI_ID_BUTTON9:
      58. WM_SetUntouchable(newWin, 0);
      59. GUI_EndDialog(pMsg->hWin, 0);
      60. GUI_EndDialog(derWin_1, 0);
      61. break;
      62. }
      63. break;
      64. }
      65. break;
      67. default:
      68. WM_DefaultProc(pMsg);
      69. break;
      70. }
      71. }
      73. static void _cbNew(WM_MESSAGE * pMsg) {
      75. switch (pMsg->MsgId) {
      77. case WM_NOTIFY_PARENT:
      78. switch (pMsg->Data.v) {
      80. case WM_NOTIFICATION_RELEASED:
      81. switch (WM_GetId(pMsg->hWinSrc)) {
      83. case GUI_ID_BUTTON0:
      84. WM_SetUntouchable(pMsg->hWin, 1);
      85. derWin_2 = GUI_CreateDialogBox(_aDer_2, GUI_COUNTOF(_aDer_2), _cbDer_2, WM_HBKWIN, 0, 0);
      86. FRAMEWIN_SetClientColor(derWin_2, GUI_YELLOW);
      87. WM_DisableWindow(derWin_2);
      88. derWin_1 = GUI_CreateDialogBox(_aDer_1, GUI_COUNTOF(_aDer_1), NULL, WM_HBKWIN, 0, 0);
      89. break;
      91. case GUI_ID_BUTTON1:
      92. GUI_EndDialog(pMsg->hWin, 0);
      93. break;
      94. }
      95. break;
      96. }
      97. break;
      99. default:
      100. WM_DefaultProc(pMsg);
      101. break;
      102. }
      103. }
      105. static void _cbBottom(WM_MESSAGE * pMsg) {
      107. switch (pMsg->MsgId) {
      109. case WM_INIT_DIALOG:
      110. FRAMEWIN_SetClientColor(pMsg->hWin, GUI_GRAY);
      111. break;
      113. case WM_NOTIFY_PARENT:
      114. switch (pMsg->Data.v) {
      116. case WM_NOTIFICATION_RELEASED:
      117. switch (WM_GetId(pMsg->hWinSrc)) {
      119. case GUI_ID_BUTTON0:
      120. newWin = GUI_CreateDialogBox(_aNew, GUI_COUNTOF(_aNew), _cbNew, WM_HBKWIN, 0, 0);
      121. break;
      122. }
      123. break;
      124. }
      125. break;
      127. default:
      128. WM_DefaultProc(pMsg);
      129. break;
      130. }
      131. }
      133. void MainTask(void) {
      134. GUI_Init();
      135. WM_SetBkWindowColor(GUI_WHITE);
      137. bottomWin = GUI_CreateDialogBox(_aBottom, GUI_COUNTOF(_aBottom), _cbBottom, WM_HBKWIN, 0, 0);
      139. while (1) {
      140. GUI_Delay(100);
      141. };
      142. }
      Display All
      Best regards,
      Volodymyr.

    • Hi Volodymyr,

      yes, this behavior is correct. Calling WM_SetUntouchable() to make a window untouchable means that the PID info doesn't get send to the untouchable window, but to any window behind the untouchable window that isn't marked untouchable. It's exactly how the untouchable mode for a window should work.

      The bottomWin was never marked untouchable, so it receives the PID info.

      Best regards,

      Florian
      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.