GUI_CreateDialogBox() do nothing on screen

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

    • GUI_CreateDialogBox() do nothing on screen

      Hi to all,

      I'm using STEMWIN (a precompiled library for ST product) on STM32F103.


      the use of the lines indicated in the manual give the expected output

      C Source Code

      1. GUI_SetFont(&GUI_Font8x16);
      2. GUI_SetBkColor(GUI_BLUE);
      3. GUI_Clear();
      4. GUI_SetPenSize(10);
      5. GUI_SetColor(GUI_RED);
      6. GUI_DrawLine(80, 10, 240, 90);
      7. GUI_DrawLine(80, 90, 240, 10);
      8. GUI_SetBkColor(GUI_BLACK);
      9. GUI_SetColor(GUI_WHITE);
      10. GUI_SetTextMode(GUI_TM_NORMAL);
      11. GUI_DispStringHCenterAt("GUI_TM_NORMAL" , 160, 10);
      12. GUI_SetTextMode(GUI_TM_REV);
      13. GUI_DispStringHCenterAt("GUI_TM_REV" , 160, 26);
      14. GUI_SetTextMode(GUI_TM_TRANS);
      15. GUI_DispStringHCenterAt("GUI_TM_TRANS" , 160, 42);
      16. GUI_SetTextMode(GUI_TM_XOR);
      17. GUI_DispStringHCenterAt("GUI_TM_XOR" , 160, 58);
      18. GUI_SetTextMode(GUI_TM_TRANS | GUI_TM_REV);
      19. GUI_DispStringHCenterAt("GUI_TM_TRANS | GUI_TM_REV", 160, 74);
      Display All




      But when I use GUIUILDER and call CreateWindow(), nothing appear on sreen. CreateWindows() execute and rturn de handler, but there is no call to function read/write.
      What I must configure before call CreateWindows() ?

      some code.
      main:

      C Source Code

      1. __HAL_RCC_CRC_CLK_ENABLE();
      4. GUI_Init();
      5. WM_MULTIBUF_Enable(1);
      6. GUI_SetLayerVisEx(1, 1);
      7. GUI_SelectLayer(1);
      8. CreateWindow();


      LCD_init:

      C Source Code

      1. void LCD_X_Config(void) {
      2. GUI_DEVICE * pDevice;
      3. CONFIG_FLEXCOLOR Config = {0};
      4. GUI_PORT_API PortAPI = {0};
      5. //
      6. // Set display driver and color conversion
      7. //
      8. pDevice = GUI_DEVICE_CreateAndLink(GUIDRV_FLEXCOLOR, GUICC_565, 0, 0);//16bit color flexcolor driver
      9. //
      10. // Display driver configuration, required for Lin-driver
      11. //
      12. LCD_SetSizeEx (0, XSIZE_PHYS , YSIZE_PHYS);
      13. LCD_SetVSizeEx(0, VXSIZE_PHYS, VYSIZE_PHYS);
      14. //
      15. // Orientation
      16. //
      17. Config.Orientation = GUI_SWAP_XY;
      18. GUIDRV_FlexColor_Config(pDevice, &Config);
      19. //
      20. // Set controller and operation mode
      21. //
      22. PortAPI.pfWrite8_A0 = LcdWriteReg;
      23. PortAPI.pfWrite8_A1 = LcdWriteData;
      24. PortAPI.pfWriteM8_A1 = LcdWriteDataMultiple;
      25. PortAPI.pfRead8_A1 = LcdReadReg;
      26. PortAPI.pfReadM8_A1 = LcdReadDataMultiple;
      27. /*
      28. PortAPI.pfWrite16_A0 = LcdWriteReg;
      29. PortAPI.pfWrite16_A1 = LcdWriteData;
      30. PortAPI.pfWriteM16_A1 = LcdWriteDataMultiple;
      31. PortAPI.pfReadM16_A1 = LcdReadDataMultiple;
      32. */
      34. //GUIDRV_FLEXCOLOR_F66709 -> Driver for ili9341
      35. //GUIDRV_FLEXCOLOR_M16C0B8 -> 16bpp, no cache, 8 bitbus
      36. GUIDRV_FlexColor_SetFunc(pDevice, &PortAPI, GUIDRV_FLEXCOLOR_F66709, GUIDRV_FLEXCOLOR_M16C0B8);//ILI9341, 16bit color, 8 bit bus, no cache
      37. }
      Display All
      Output of Guibuilder:

      C Source Code

      1. /*********************************************************************
      2. * *
      3. * SEGGER Microcontroller GmbH & Co. KG *
      4. * Solutions for real time microcontroller applications *
      5. * *
      6. **********************************************************************
      7. * *
      8. * C-file generated by: *
      9. * *
      10. * GUI_Builder for emWin version 5.44 *
      11. * Compiled Nov 10 2017, 08:53:57 *
      12. * (c) 2017 Segger Microcontroller GmbH & Co. KG *
      13. * *
      14. **********************************************************************
      15. * *
      16. * Internet: www.segger.com Support: support@segger.com *
      17. * *
      18. **********************************************************************
      19. */
      21. // USER START (Optionally insert additional includes)
      22. // USER END
      24. #include "DIALOG.h"
      26. /*********************************************************************
      27. *
      28. * Defines
      29. *
      30. **********************************************************************
      31. */
      32. #define ID_WINDOW_0 (GUI_ID_USER + 0x04)
      33. #define ID_BUTTON_0 (GUI_ID_USER + 0x05)
      36. // USER START (Optionally insert additional defines)
      37. // USER END
      39. /*********************************************************************
      40. *
      41. * Static data
      42. *
      43. **********************************************************************
      44. */
      46. // USER START (Optionally insert additional static data)
      47. // USER END
      49. /*********************************************************************
      50. *
      51. * _aDialogCreate
      52. */
      53. static const GUI_WIDGET_CREATE_INFO _aDialogCreate[] = {
      54. { WINDOW_CreateIndirect, "Window", ID_WINDOW_0, 0, 0, 320, 240, 0, 0x0, 0 },
      55. { BUTTON_CreateIndirect, "Button", ID_BUTTON_0, 118, 93, 80, 20, 0, 0x0, 0 },
      56. // USER START (Optionally insert additional widgets)
      57. // USER END
      58. };
      60. /*********************************************************************
      61. *
      62. * Static code
      63. *
      64. **********************************************************************
      65. */
      67. // USER START (Optionally insert additional static code)
      68. // USER END
      70. /*********************************************************************
      71. *
      72. * _cbDialog
      73. */
      74. static void _cbDialog(WM_MESSAGE * pMsg) {
      75. WM_HWIN hItem;
      76. int NCode;
      77. int Id;
      78. // USER START (Optionally insert additional variables)
      79. // USER END
      81. switch (pMsg->MsgId) {
      82. case WM_INIT_DIALOG:
      83. //
      84. // Initialization of 'Window'
      85. //
      86. hItem = pMsg->hWin;
      87. WINDOW_SetBkColor(hItem, GUI_MAKE_COLOR(0x0000FF00));
      88. // USER START (Optionally insert additional code for further widget initialization)
      89. // USER END
      90. break;
      91. case WM_NOTIFY_PARENT:
      92. Id = WM_GetId(pMsg->hWinSrc);
      93. NCode = pMsg->Data.v;
      94. switch(Id) {
      95. case ID_BUTTON_0: // Notifications sent by 'Button'
      96. switch(NCode) {
      97. case WM_NOTIFICATION_CLICKED:
      98. // USER START (Optionally insert code for reacting on notification message)
      99. // USER END
      100. break;
      101. case WM_NOTIFICATION_RELEASED:
      102. // USER START (Optionally insert code for reacting on notification message)
      103. // USER END
      104. break;
      105. // USER START (Optionally insert additional code for further notification handling)
      106. // USER END
      107. }
      108. break;
      109. // USER START (Optionally insert additional code for further Ids)
      110. // USER END
      111. }
      112. break;
      113. // USER START (Optionally insert additional message handling)
      114. // USER END
      115. default:
      116. WM_DefaultProc(pMsg);
      117. break;
      118. }
      119. }
      121. /*********************************************************************
      122. *
      123. * Public code
      124. *
      125. **********************************************************************
      126. */
      127. /*********************************************************************
      128. *
      129. * CreateWindow
      130. */
      131. WM_HWIN CreateWindow(void);
      132. WM_HWIN CreateWindow(void) {
      133. WM_HWIN hWin;
      135. hWin = GUI_CreateDialogBox(_aDialogCreate, GUI_COUNTOF(_aDialogCreate), _cbDialog, WM_HBKWIN, 0, 0);
      136. return hWin;
      137. }
      139. // USER START (Optionally insert additional public code)
      140. // USER END
      142. /*************************** End of file ****************************/
      Display All
      Whats wrong with GUIBuilder ?


      I know that now exist app builder, but the license issued by ST cover only GIBulder

    • Hi,

      Does your MainTask() have a superloop? The superloop is necessary so that emWin is "kept alive" and interactions with widgets work. This is due to the callback mechanism of emWin.

      After GUI_Init() is called and all your calls in MainTask() are done, the application should run in a loop like this:

      C Source Code

      1. while (1) {
      2. GUI_Delay(100);
      3. }
      Simple operations such as line drawing or displaying strings do not require a superloop.

      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.

    • Hi Florian,

      thanks for your help.
      By adding a superloop with GUI_Delay everything works fine.
      In my project I don't have a superloop where to call the GUI_Delay() function, can I use GUI_Exec() instead and call it only when I need to update the screen (obviously the touch will not work in this configuration)?

    • Hi,

      Yes, you can do that. Maybe like this:

      C Source Code

      1. CreateWindow()
      2. GUI_Exec()
      3. DeleteWindow()
      4. CreateAnotherWindoW()
      5. GUI_Exec()
      But without a loop you can not do things like animations ore create timer with emWin.



      Also, do not call GUI_Exec() from a callback function of a window.

      BTW, the following three calls shouldn't be required:

      C Source Code

      1. WM_MULTIBUF_Enable(1);
      2. GUI_SetLayerVisEx(1, 1);
      3. GUI_SelectLayer(1);

      Multibuffering is not available when using the GUIDRV_FlexColor driver.
      The layer specific calls are not required if using only one layer. Anyway, since you have only one layer you had to call these function with LayerIndex == 0. ;)

      Regards,
      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.