MULTIPAGE issue #1 of not focusable page

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

    • MULTIPAGE issue #1 of not focusable page

      Hello.

      I found the issue of MULTIPAGE-widget.
      If some page does not contain any focusable element (for example only TEXT or disabled all widgets) there is a coloring issue:

      if to return from this page to other page which contains the focusable element(s) then this focusable widget will not have a "focusable" color.

      A simple example demonstrates this issue.
      If you select page 1, then select page 2 and then select page 1 again you will see that no one button is colored as focused.

      This issue is present even in ver. 5.50.

      Question: What API-function or message informs that a page of MULTIPAGE was selected?

      C Source Code

      1. #include "GUI.h"
      2. #include "MULTIPAGE.h"
      4. /*********************************************************************
      5. * Defines
      6. **********************************************************************
      7. */
      8. // Recommended memory to run the sample with adequate performance
      9. //
      10. #define RECOMMENDED_MEMORY (1024L * 20)
      12. /*********************************************************************
      13. * Dialog resource
      14. *
      15. * These tables contain the information required to create the dialogs.
      16. * It has been created manually, but could also be created by the GUIBuilder.
      17. */
      18. static const GUI_WIDGET_CREATE_INFO _aDialogCreate1[] = {
      19. { WINDOW_CreateIndirect, NULL, 0, 0, 0, 260, 100, FRAMEWIN_CF_MOVEABLE },
      20. { TEXT_CreateIndirect, "Dialog 1", 0, 5, 10, 50, 20, TEXT_CF_LEFT },
      21. { BUTTON_CreateIndirect, "Button 1", GUI_ID_BUTTON0, 5, 30, 80, 20, 0},
      22. { BUTTON_CreateIndirect, "Button 1", GUI_ID_BUTTON1, 5, 60, 80, 20, 0},
      23. };
      25. static const GUI_WIDGET_CREATE_INFO _aDialogCreate2[] = {
      26. { WINDOW_CreateIndirect, NULL, 0, 0, 0, 260, 100, FRAMEWIN_CF_MOVEABLE },
      27. { TEXT_CreateIndirect, "Dialog 2", 0, 5, 10, 50, 20, TEXT_CF_LEFT },
      28. { TEXT_CreateIndirect, "Text 1", GUI_ID_TEXT0, 25, 30, 50, 15, TEXT_CF_LEFT },
      29. { TEXT_CreateIndirect, "Text 2", GUI_ID_TEXT1, 25, 50, 50, 15, TEXT_CF_LEFT },
      30. };
      32. static const GUI_WIDGET_CREATE_INFO _aDialogCreate3[] = {
      33. { WINDOW_CreateIndirect, NULL, 0, 0, 0, 260, 100, FRAMEWIN_CF_MOVEABLE },
      34. { TEXT_CreateIndirect, "Dialog 3", 0, 5, 10, 50, 20, TEXT_CF_LEFT },
      35. { RADIO_CreateIndirect, "", GUI_ID_RADIO0, 5, 30, 0, 0, 0, 3},
      36. { TEXT_CreateIndirect, "Option 1", GUI_ID_TEXT0, 25, 30, 50, 15, TEXT_CF_LEFT },
      37. { TEXT_CreateIndirect, "Option 2", GUI_ID_TEXT1, 25, 50, 50, 15, TEXT_CF_LEFT },
      38. { TEXT_CreateIndirect, "Option 3", GUI_ID_TEXT2, 25, 70, 50, 15, TEXT_CF_LEFT },
      39. };
      41. /*********************************************************************
      42. * Public code
      43. **********************************************************************
      44. */
      45. /*********************************************************************
      46. * MainTask
      47. */
      48. void MainTask(void) {
      49. WM_HWIN hMultiPage;
      50. WM_HWIN hFrameWin;
      51. WM_HWIN hDialog;
      52. //
      53. // Enable use of memory devices
      54. //
      55. WM_SetCreateFlags(WM_CF_MEMDEV);
      56. GUI_Init();
      57. //
      58. // Check if recommended memory for the sample is available
      59. //
      60. if (GUI_ALLOC_GetNumFreeBytes() < RECOMMENDED_MEMORY) {
      61. GUI_ErrorOut("Not enough memory available.");
      62. return;
      63. }
      64. //
      65. // Create the frame window
      66. //
      67. hFrameWin = FRAMEWIN_Create("FrameWindow", NULL, WM_CF_SHOW, 40, 44, 240, 152);
      68. FRAMEWIN_SetClientColor(hFrameWin, GUI_GREEN);
      69. FRAMEWIN_SetActive(hFrameWin, 1);
      70. FRAMEWIN_SetMoveable(hFrameWin, 1);
      71. //
      72. // Create the MULTIPAGE widget
      73. //
      74. hMultiPage = MULTIPAGE_CreateEx(7, 6, 220, 120, WM_GetClientWindow(hFrameWin), WM_CF_SHOW, 0, 0);
      75. //
      76. // Create and attach the MULTIPAGE dialog windows
      77. //
      78. hDialog = GUI_CreateDialogBox(_aDialogCreate1, GUI_COUNTOF(_aDialogCreate1), NULL, WM_UNATTACHED, 0, 0);
      79. MULTIPAGE_AddPage(hMultiPage, hDialog, "Page 1");
      80. hDialog = GUI_CreateDialogBox(_aDialogCreate2, GUI_COUNTOF(_aDialogCreate2), NULL, WM_UNATTACHED, 0, 0);
      81. MULTIPAGE_AddPage(hMultiPage, hDialog, "Page 2");
      82. hDialog = GUI_CreateDialogBox(_aDialogCreate3, GUI_COUNTOF(_aDialogCreate3), NULL, WM_UNATTACHED, 0, 0);
      83. MULTIPAGE_AddPage(hMultiPage, hDialog, "Page 3");
      84. while (1) {
      85. GUI_Delay(100);
      86. }
      87. }
      88. /*************************** End of file ****************************/
      Display All
      Best regards,
      Volodymyr.

      The post was edited 1 time, last by volodymyr ().

    • Hi Volodymyr,

      thank you for reporting this issue, we will fix that. About your question, when a new page is selected, a WM_NOTIFICATION_VALUE_CHANGED notification will be sent and the selection will be changed via MULTIPAGE_SelectPage().

      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.

      The post was edited 1 time, last by SEGGER - Florian ().

    • SEGGER - Florian wrote:

      About your question, when a new page is selected, a WM_NOTIFICATION_VALUE_CHANGED will be sent and the selection will be changed via MULTIPAGE_SelectPage().
      Hi Florian.

      Is there a way to get a message about new selected page from assigned callback-function of MULTIPAGE-widget, not from callback of its parent window?

      Or how can I fix this issue with color of focused object, what is the best way?
      Best regards,
      Volodymyr.

      The post was edited 1 time, last by volodymyr ().

    • Hi Volodymyr,

      yes, this is doable. WM_NOTIFICATION_VALUE_CHANGED is the value of a WM_NOTIFY_PARENT message. That message gets sent to the parent window, as the name indicates. But you can of course send the message to any other window you'd like to.
      This is how you do it:

      C Source Code

      1. #include "GUI.h"
      2. #include "MULTIPAGE.h"
      4. /*********************************************************************
      5. *
      6. * Static data
      7. *
      8. **********************************************************************
      9. */
      10. static WM_HWIN _hMulti;
      12. static const GUI_WIDGET_CREATE_INFO _aDialogCreate1[] = {
      13. { WINDOW_CreateIndirect, NULL, 0, 0, 0, 260, 100, FRAMEWIN_CF_MOVEABLE },
      14. { TEXT_CreateIndirect, "Dialog 1", GUI_ID_TEXT0, 5, 10, 50, 20, TEXT_CF_LEFT },
      15. { BUTTON_CreateIndirect, "Button 1", GUI_ID_BUTTON0, 5, 30, 80, 20, 0 },
      16. { BUTTON_CreateIndirect, "Button 2", GUI_ID_BUTTON1, 5, 60, 80, 20, 0 },
      17. };
      18. static const GUI_WIDGET_CREATE_INFO _aDialogCreate2[] = {
      19. { WINDOW_CreateIndirect, NULL, 0, 0, 0, 260, 100, FRAMEWIN_CF_MOVEABLE },
      20. { TEXT_CreateIndirect, "Dialog 2", GUI_ID_TEXT1, 5, 10, 50, 20, TEXT_CF_LEFT },
      21. { TEXT_CreateIndirect, "Text 1", GUI_ID_TEXT2, 25, 30, 50, 15, TEXT_CF_LEFT },
      22. { TEXT_CreateIndirect, "Text 2", GUI_ID_TEXT3, 25, 50, 50, 15, TEXT_CF_LEFT },
      23. };
      24. static const GUI_WIDGET_CREATE_INFO _aDialogCreate3[] = {
      25. { WINDOW_CreateIndirect, NULL, 0, 0, 0, 260, 100, FRAMEWIN_CF_MOVEABLE },
      26. { TEXT_CreateIndirect, "Dialog 3", GUI_ID_TEXT4, 5, 10, 50, 20, TEXT_CF_LEFT },
      27. { RADIO_CreateIndirect, "", GUI_ID_RADIO0, 5, 30, 0, 0, 0, 3 },
      28. { TEXT_CreateIndirect, "Option 1", GUI_ID_TEXT5, 25, 30, 50, 15, TEXT_CF_LEFT },
      29. { TEXT_CreateIndirect, "Option 2", GUI_ID_TEXT6, 25, 50, 50, 15, TEXT_CF_LEFT },
      30. { TEXT_CreateIndirect, "Option 3", GUI_ID_TEXT7, 25, 70, 50, 15, TEXT_CF_LEFT },
      31. };
      33. /*********************************************************************
      34. *
      35. * Static code
      36. *
      37. **********************************************************************
      38. */
      39. /*********************************************************************
      40. *
      41. * _cbBk
      42. */
      43. static void _cbBk(WM_MESSAGE * pMsg) {
      44. switch (pMsg->MsgId) {
      45. case WM_NOTIFY_PARENT:
      46. //
      47. // If we got the corrent notification, send it to the MULTIPAGE widget.
      48. //
      49. if (pMsg->Data.v == WM_NOTIFICATION_VALUE_CHANGED) {
      50. WM_SendMessage(_hMulti, pMsg);
      51. }
      52. break;
      53. default:
      54. WM_DefaultProc(pMsg);
      55. break;
      56. }
      57. }
      59. /*********************************************************************
      60. *
      61. * _cbMulti
      62. */
      63. static void _cbMulti(WM_MESSAGE * pMsg) {
      64. switch (pMsg->MsgId) {
      65. case WM_NOTIFY_PARENT:
      66. //
      67. // Check if it is the correct notification.
      68. //
      69. if (pMsg->Data.v == WM_NOTIFICATION_VALUE_CHANGED) {
      70. //
      71. // Do something...
      72. //
      73. }
      74. break;
      75. default:
      76. MULTIPAGE_Callback(pMsg);
      77. break;
      78. }
      79. }
      81. /*********************************************************************
      82. *
      83. * Public code
      84. *
      85. **********************************************************************
      86. */
      87. /*********************************************************************
      88. *
      89. * MainTask
      90. */
      91. void MainTask(void) {
      92. WM_HWIN hDialog;
      94. //
      95. // Init GUI
      96. //
      97. GUI_Init();
      98. //
      99. // Create a parent window or set callback to background
      100. //
      101. WM_SetCallback(WM_HBKWIN, _cbBk);
      102. //
      103. // Create multipage widget
      104. //
      105. _hMulti = MULTIPAGE_CreateEx(7, 6, 220, 120, WM_HBKWIN, WM_CF_SHOW, 0, 0);
      106. //
      107. // Set custom callback to multipage widget
      108. //
      109. WM_SetCallback(_hMulti, _cbMulti);
      110. //
      111. // Create and attach the MULTIPAGE dialog windows
      112. //
      113. hDialog = GUI_CreateDialogBox(_aDialogCreate1, GUI_COUNTOF(_aDialogCreate1), NULL, WM_UNATTACHED, 0, 0);
      114. MULTIPAGE_AddPage(_hMulti, hDialog, "Page 1");
      115. hDialog = GUI_CreateDialogBox(_aDialogCreate2, GUI_COUNTOF(_aDialogCreate2), NULL, WM_UNATTACHED, 0, 0);
      116. MULTIPAGE_AddPage(_hMulti, hDialog, "Page 2");
      117. hDialog = GUI_CreateDialogBox(_aDialogCreate3, GUI_COUNTOF(_aDialogCreate3), NULL, WM_UNATTACHED, 0, 0);
      118. MULTIPAGE_AddPage(_hMulti, hDialog, "Page 3");
      120. while (1) {
      121. GUI_Delay(100);
      122. }
      123. }
      Display All



      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.

    • SEGGER - Florian wrote:

      yes, this is doable.

      Hi Florian.

      Your way is not usable for me because I create multiple nested MULTIPAGEs (several MULTIPAGEs inside each of tab of top MULTIPAGE, see pictures), so I do not use the WINDOW handle of each nested MULTIPAGE, I am working only with and inside MULTIPAGE's callbacks.

      By the way, this above mentioned issue with MULTIPAGE concerns not only to the color.
      If there is a page with no focusable element and if this page is selected, but the keyboard-activity is applied to another tab, which contains focusable objects.
      Images

      • 00.png

        21.84 kB, 640×480, viewed 493 times

      • 01.png

        21.82 kB, 640×480, viewed 473 times

      • 02.png

        18.11 kB, 640×480, viewed 486 times
      Best regards,
      Volodymyr.