Hello,
We are running emWin under FreeeRTOS. As part of the application, a blocking dialog is executed under a child window. Prior to doing so however, a timer is created to detect a period of inactivity, after which the timer callback executes WM_Delete for the underlying parent window, essentially as a mechanism to restore normal operation after a period of inactivity.
I am curious what happens to the calling function and it's stack that contains the GUI_ExecDialogDox() when WM_DeleteWindow() executed on an underlying parent window as a result of a RTOS timer callback? I have set breakpoints on the other side of the GUI_ExecDialog() that do not trip in this scenario. Is this potentially a memory leak?
We are running emWin under FreeeRTOS. As part of the application, a blocking dialog is executed under a child window. Prior to doing so however, a timer is created to detect a period of inactivity, after which the timer callback executes WM_Delete for the underlying parent window, essentially as a mechanism to restore normal operation after a period of inactivity.
I am curious what happens to the calling function and it's stack that contains the GUI_ExecDialogDox() when WM_DeleteWindow() executed on an underlying parent window as a result of a RTOS timer callback? I have set breakpoints on the other side of the GUI_ExecDialog() that do not trip in this scenario. Is this potentially a memory leak?