How to increase GUIX performance when using gx_widget_show/hide

Question

How to increase GUIX performance when using gx_widget_show/hide

Kwon 20

I have a window with 4 subwindows covering the same area on the canvas, each subwindow with ~50 nested widgets. The UI is controlled by a state machine executing every 40ms processing any touch events that the state machine consumes and subsequently calls the gx_widget_show/gx_widget_hide APIs on the subwindows. Calling gx_widget_show(subwindow_1) is instant, however calling gx_widget_hide(subwindow_1) and then gx_widget_show(subwindow_2) takes significantly longer(~1second). Is there any recommendation on how to improve this process?

Kwon 20 Reputation points

2023-06-27T20:21:14.36+00:00

Upon further investigation it seems like the state machine thread is interfering with the gx_system thread.

The call to gx_widget_show(subwindow_2) executes at timestamp 03766844(ms) and does not display until timestamp 03767470(ms).
LeelaRajeshSayana-MSFT 17,866 Reputation points Moderator

2023-06-27T23:13:13.0266667+00:00

Hi @Kwon Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here. Our community SMEs will review this issue and get back to as soon as possible.
Anonymous

2023-06-29T07:01:11.65+00:00

What is the priority of the state machine thread in relation to the GUIX thread? If the state machine thread has a lower priority, my assumption is that after calling gx_widget_hide(subwindow_1), the thread might be preempted by the GUIX thread, resulting in the screen being refreshed. Consequently, the execution of gx_widget_show(subwindow_2) would occur after the refresh is complete. This implies that calling gx_widget_hide and gx_widget_show consecutively could potentially trigger GUIX refreshing twice. To investigate this further, could you try placing the hide and show calls within the GUIX thread, such as in an event processing function, and observe if the same behavior occurs?
LeelaRajeshSayana-MSFT 17,866 Reputation points Moderator

2023-07-05T14:29:07.4166667+00:00

Hi @Kwon Greetings! I am following up to see if you got a chance to review the below response. Please let us know if you have any additional questions or need further assistance.

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.
Kwon 20 Reputation points

2023-07-07T23:18:09.1133333+00:00

I tried to change my priority settings with my state machine being the highest priority and then the GUIX system being the high priority the timing issue between when a widget is displayed still exists:

For some reason GUIX system thread does not run when I request to show
Anonymous

2023-07-10T03:35:56.79+00:00

Does the 100Hz Task thread represent your state machine thread? Based on the provided screenshot, it appears that the 100Hz Task thread has a lower priority compared to the GUIX system thread. If the state machine is assigned a higher priority, there is a possibility of blocking the GUIX system thread. Have you attempted calling widget hide and show functions within the GUIX system thread? For instance, you could send an event to the GUIX system thread and handle it within that thread to execute the widget hide and show operations.

Kwon 20

I created an event like so:

void show_setting_window(void)
{
    GX_EVENT gxe;
    gxe.gx_event_sender = SENDER_PCU;
    gxe.gx_event_target = get_window(GuiState->currWindow);
    gxe.gx_event_display_handle = 0;
    gxe.gx_event_type = APP_EVENT_SHOW_SETTING_WINDOW;
    gx_system_event_send(&gxe);
}

and then in the event handlers I added a case

case APP_EVENT_SHOW_SETTING_WINDOW:
{ 
    gx_widget_show(&therapy_window.therapy_window_black_window);              
    gx_widget_show(&therapy_window.therapy_window_device_settings_subwindow);
    break;        
}

However there is still a ~1 second delay when showing

Kwon 20

Edit: That is correct, my state machine runs in the 100Hz tasks

I added the user event like so:

void show_setting_window(void)
{
    GX_EVENT gxe;
    gxe.gx_event_sender = SENDER_PCU;
    gxe.gx_event_target = get_window(GuiState->currWindow);
    gxe.gx_event_display_handle = 0;
    gxe.gx_event_type = APP_EVENT_SHOW_SETTING_WINDOW;
    gx_system_event_send(&gxe);
}

and then in my event handler I added

        case APP_EVENT_SHOW_SETTING_WINDOW:
        {
            gx_widget_show(&therapy_window.therapy_window_black_window);
            gx_widget_show(&therapy_window.therapy_window_device_settings_subwindow);
            break;
        }

However there is still a ~1 second delay when showing

Anonymous

2023-07-13T03:02:56.39+00:00

Hi Kwon, Would it be possible to send your project to me so I can further investigate the issue?
Kwon 20 Reputation points

2023-07-13T15:38:21.85+00:00

Unfortunately this is not possible. I am am only allowed to share some snippets

1 answer

Your answer

Kwon 20 Reputation points

2023-06-27T20:21:14.36+00:00

Upon further investigation it seems like the state machine thread is interfering with the gx_system thread.

The call to gx_widget_show(subwindow_2) executes at timestamp 03766844(ms) and does not display until timestamp 03767470(ms).
LeelaRajeshSayana-MSFT 17,866 Reputation points Moderator

2023-06-27T23:13:13.0266667+00:00

Hi @Kwon Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here. Our community SMEs will review this issue and get back to as soon as possible.
Anonymous

2023-06-29T07:01:11.65+00:00

What is the priority of the state machine thread in relation to the GUIX thread? If the state machine thread has a lower priority, my assumption is that after calling gx_widget_hide(subwindow_1), the thread might be preempted by the GUIX thread, resulting in the screen being refreshed. Consequently, the execution of gx_widget_show(subwindow_2) would occur after the refresh is complete. This implies that calling gx_widget_hide and gx_widget_show consecutively could potentially trigger GUIX refreshing twice. To investigate this further, could you try placing the hide and show calls within the GUIX thread, such as in an event processing function, and observe if the same behavior occurs?
LeelaRajeshSayana-MSFT 17,866 Reputation points Moderator

2023-07-05T14:29:07.4166667+00:00

Hi @Kwon Greetings! I am following up to see if you got a chance to review the below response. Please let us know if you have any additional questions or need further assistance.

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.
Kwon 20 Reputation points

2023-07-07T23:18:09.1133333+00:00

I tried to change my priority settings with my state machine being the highest priority and then the GUIX system being the high priority the timing issue between when a widget is displayed still exists:

For some reason GUIX system thread does not run when I request to show
Anonymous

2023-07-10T03:35:56.79+00:00

Does the 100Hz Task thread represent your state machine thread? Based on the provided screenshot, it appears that the 100Hz Task thread has a lower priority compared to the GUIX system thread. If the state machine is assigned a higher priority, there is a possibility of blocking the GUIX system thread. Have you attempted calling widget hide and show functions within the GUIX system thread? For instance, you could send an event to the GUIX system thread and handle it within that thread to execute the widget hide and show operations.
Kwon 20 Reputation points

2023-07-10T18:25:07.4633333+00:00

I created an event like so:

void show_setting_window(void) { GX_EVENT gxe; gxe.gx_event_sender = SENDER_PCU; gxe.gx_event_target = get_window(GuiState->currWindow); gxe.gx_event_display_handle = 0; gxe.gx_event_type = APP_EVENT_SHOW_SETTING_WINDOW; gx_system_event_send(&gxe); }

and then in the event handlers I added a case

case APP_EVENT_SHOW_SETTING_WINDOW: { gx_widget_show(&therapy_window.therapy_window_black_window); gx_widget_show(&therapy_window.therapy_window_device_settings_subwindow); break; }

However there is still a ~1 second delay when showing
Kwon 20 Reputation points

2023-07-10T18:27:27.76+00:00

Edit: That is correct, my state machine runs in the 100Hz tasks

I added the user event like so:

void show_setting_window(void) { GX_EVENT gxe; gxe.gx_event_sender = SENDER_PCU; gxe.gx_event_target = get_window(GuiState->currWindow); gxe.gx_event_display_handle = 0; gxe.gx_event_type = APP_EVENT_SHOW_SETTING_WINDOW; gx_system_event_send(&gxe); }

and then in my event handler I added

case APP_EVENT_SHOW_SETTING_WINDOW: { gx_widget_show(&therapy_window.therapy_window_black_window); gx_widget_show(&therapy_window.therapy_window_device_settings_subwindow); break; }

However there is still a ~1 second delay when showing
Anonymous

2023-07-13T03:02:56.39+00:00

Hi Kwon, Would it be possible to send your project to me so I can further investigate the issue?
Kwon 20 Reputation points

2023-07-13T15:38:21.85+00:00

Unfortunately this is not possible. I am am only allowed to share some snippets

Answer 1

What is the priority of the state machine thread in relation to the GUIX thread? If the state machine thread has a lower priority, my assumption is that after calling gx_widget_hide(subwindow_1), the thread might be preempted by the GUIX thread, resulting in the screen being refreshed. gx_widget_show(subwindow_2) will get execution after the refresh is complete. This implies that calling gx_widget_hide and gx_widget_show consecutively could potentially trigger GUIX refreshing twice. To investigate this further, could you try placing the hide and show calls within the GUIX thread, such as in an event processing function, and observe if the same behavior occurs?

Share via

How to increase GUIX performance when using gx_widget_show/hide

1 answer

Your answer