[SOLVED] Possibilities to refresh a graph in background

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

    • [SOLVED] Possibilities to refresh a graph in background

      Hello everybody,

      I have following problem:

      I want to visualize ADC-Values as a Graph.
      Every x ms a new value from the ADC is sampled and visualized.
      The shown data is correct ---> So everything works fine.

      But if I switch to another dialog and come back to the "graph screen" the values are gone. I think the whole dialog is newly created. But how can I manage that?
      Logging data in the background and draw graph if the screen is created? Is there any possibility not to kill that dialog while another dialog is shown? (I tried to create all dialogs/windows once and call them by GUI_ExecCreatedDialog() but that does not work)
      What do you think?

      Image0 ---> after switching back
      Image1 ---> while being on the screen


      Code snippet of the "graph screen":

      C Source Code

      1. static void _cbScreen3(WM_MESSAGE * pMsg)
      2. {
      3. WM_HWIN hItem;
      4. int NCode,Id;
      6. static GRAPH_DATA_Handle hGraph1, hGraph2;
      7. int Value;
      8. static int Angle;
      9. static int Stop;
      10. static WM_HTIMER hTimer1;
      11. GRAPH_SCALE_Handle hScaley;
      12. GRAPH_SCALE_Handle hScalex;
      13. int NumItems;
      15. switch (pMsg->MsgId)
      16. {
      17. case WM_INIT_DIALOG:
      18. hItem = pMsg->hWin;
      19. WINDOW_SetBkColor(hItem, GUI_WHITE);
      20. hItem = WM_GetDialogItem(pMsg->hWin, ID_TEXT_30);
      21. TEXT_SetTextAlign(hItem, TEXT_CF_LEFT);
      22. TEXT_SetTextColor(hItem, GUI_BLUE);
      23. TEXT_SetFont(hItem, GUI_FONT_24B_1);
      24. TEXT_SetText(hItem, "Graph");
      25. hItem = WM_GetDialogItem(pMsg->hWin, ID_BUTTON_BACK_MENU_3);
      26. BUTTON_SetText(hItem, "Menu");
      27. BUTTON_SetDefaultSkin(BUTTON_SKIN_FLEX);
      28. hItem = WM_GetDialogItem(pMsg->hWin, ID_BUTTON_SCREEN_3);
      29. BUTTON_SetText(hItem, "Screen 2 ");
      31. hItem = WM_GetDialogItem(pMsg->hWin, ID_GRAPH_0);
      32. WM_SetCallback(hItem, _cbGraph);
      33. GRAPH_SetGridVis(hItem, 1); //Gatter sichtbar?
      34. GRAPH_SetColor(hItem, GUI_WHITE,GRAPH_CI_BK);
      35. GRAPH_SetColor(hItem, GUI_GREEN,GRAPH_CI_GRID);
      36. hScaley =GRAPH_SCALE_Create(5,GUI_TA_VCENTER,GRAPH_SCALE_CF_VERTICAL,10);
      37. GRAPH_SCALE_SetPos(hScaley,1);
      38. GRAPH_SCALE_SetTextColor(hScaley,GUI_BLACK);
      39. GRAPH_SCALE_SetFactor(hScaley,0.1);
      40. GRAPH_SCALE_SetTickDist(hScaley,50);
      41. GRAPH_AttachScale(hItem,hScaley);
      43. hScalex = GRAPH_SCALE_Create(5,GUI_TA_HCENTER,GRAPH_SCALE_CF_HORIZONTAL,50); //Scala für die X-Achse
      44. GRAPH_SCALE_SetPos(hScalex,140);
      45. GRAPH_SCALE_SetTextColor(hScalex,GUI_BLACK);
      46. GRAPH_SCALE_SetFactor(hScalex,0.5);
      47. GRAPH_AttachScale(hItem,hScalex);
      49. NumItems = WM_GetWindowSizeX(hItem); //--> Anzahl der Items abhängig von der Größe des Widgets (x-Achse)
      51. // 2 Datenobjekte für Graphen
      52. hGraph1 = GRAPH_DATA_YT_Create(GUI_BLUE, NumItems, NULL, 0);
      54. GRAPH_AttachData(hItem, hGraph1);
      55. // GRAPH_AttachData(hItem, hGraph2);
      56. // alle x ms ein neues Wertepaar je Graph
      57. hTimer1 = WM_CreateTimer( pMsg->hWin, 1, TIMER_VALUE, 0);
      58. break;
      60. case WM_TIMER:
      61. if (Stop == 0)
      62. {
      63. WM_RestartTimer(hTimer1, 0);
      64. }
      66. if(Mode_Timer !=1)
      67. {
      69. }
      70. GRAPH_DATA_YT_AddValue(hGraph1, g_Voltage*10);
      71. break;
      73. case MESSAGE_STARTSTOP:
      74. Stop ^= 1;
      75. if (Stop == 0)
      76. {
      77. WM_RestartTimer(hTimer1, 0);
      78. }
      79. break;
      81. case WM_NOTIFY_PARENT:
      83. Id = WM_GetId(pMsg->hWinSrc);
      84. NCode = pMsg->Data.v;
      85. switch(Id)
      86. {
      87. case ID_BUTTON_SCREEN_3:
      88. switch(NCode)
      89. {
      90. case WM_NOTIFICATION_CLICKED:
      91. break;
      92. case WM_NOTIFICATION_RELEASED:
      93. WM_DeleteWindow(pMsg->hWin);
      94. GUI_CreateDialogBox(_aScreen2Create, GUI_COUNTOF(_aScreen2Create), _cbScreen2, WM_HBKWIN, 0, 0);
      95. break;
      96. }
      97. break;
      99. case ID_BUTTON_BACK_MENU_3:
      100. switch(NCode)
      101. {
      102. case WM_NOTIFICATION_RELEASED:
      103. WM_DeleteWindow(pMsg->hWin);
      104. GUI_CreateDialogBox(_aDialogCreate, GUI_COUNTOF(_aDialogCreate), _cbDialog, WM_HBKWIN, 0, 0);
      105. break;
      106. }
      107. break;
      110. case ID_BUTTON_3: // Notifications sent by 'Iconview'
      111. switch(NCode)
      112. {
      113. case WM_NOTIFICATION_RELEASED:
      114. hItem = WM_GetDialogItem(pMsg->hWin, ID_TEXT_30);
      115. }
      116. }
      117. default:
      118. WM_DefaultProc(pMsg);
      119. break;
      120. }
      121. }
      Display All

      Example how the dialog is called:

      C Source Code

      1. case ID_BUTTON_SCREEN_1:
      2. switch(NCode)
      3. {
      4. case WM_NOTIFICATION_CLICKED:
      5. break;
      6. case WM_NOTIFICATION_RELEASED:
      7. WM_DeleteWindow(pMsg->hWin);
      8. GUI_CreateDialogBox(_aScreen3Create, GUI_COUNTOF(_aScreen3Create), _cbScreen3, WM_HBKWIN, 0, 0);
      9. break;
      10. }
      11. break;
      Display All


      Thank you very much!
      Images

      • image0.jpeg

        384.41 kB, 1,632×1,224, viewed 678 times

      • image1.jpeg

        409.37 kB, 1,632×1,224, viewed 690 times

    • Hi,

      to keep the graph data, the dialog that contains the graph handles should not be deleted.

      You could hide the graph dialog when switching to another window and show the graph dialog again when opening it.

      So instead of deleting the windows and creating them again, you could use the routines WM_HideWindow() and WM_ShowWindow().

      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.