How to prevent waveform stuttering when updating prompt widget?

Question

How to prevent waveform stuttering when updating prompt widget?

Kwon 20

trace.pngEvery 40ms I call gx_canvas_line_draw on a uint32_t data buffer and increment the eraser by 1 pixel. Any time I press a button on the screen, there is a slight stutter in the waveform. I initially thought some other high priority threads were causing the delay, but after suspending those threads the stuttering issue is still present.

Here are my current executing threads and their priorities:

Touch Thread - 6

Log Thread - 7

GUIX Thread -16

Buffer Thread - 17

Any insight or help is much appreciated

LeelaRajeshSayana-MSFT 17,521 Reputation points

2023-08-09T00:36:25.9+00:00

Hi @Kwon Greetings! Welcome to Microsoft Q&A forum. Thank you for posting the question here. Our community SMEs on this this topic will review this question and get back to you with more details as soon as possible. Please stay tuned to this for updates in the next two days.
Kwon 20 Reputation points

2023-08-13T04:49:43.5766667+00:00

We also enabled watchdog and signaled a semaphore to pet the watchdog every 150ms with the reset timeout at 300ms. During a touch event the time between watchdog pets is ~300ms. Somehow the semaphore failed to get and during this time period and the system resets :(

Kwon 20

I found that excessive inputs to the guix event queue causes the system timer thread to not execute, thus introducing delays and preventing the watchdog from getting pet. Is there any configuration to allow GUIX thread to not block other higher priority threads during many inputs?

        case GX_SIGNAL(BUTTON, GX_EVENT_TOGGLE_ON):
        {
            gx_widget_style_remove(widget1, GX_STYLE_ENABLED); 
            gx_widget_style_remove(widget2, GX_STYLE_ENABLED); 
    		gx_widget_style_remove(widget3, GX_STYLE_ENABLED);
    		gx_widget_style_remove(widget4, GX_STYLE_ENABLED);
    		gx_widget_style_remove(widget5, GX_STYLE_ENABLED);
		    gx_widget_style_remove(widget6, GX_STYLE_ENABLED);
	    	gx_widget_style_remove(widget7, GX_STYLE_ENABLED);

            gx_button_deselect(button1, false); 
			gx_button_deselect(button2, false); 
			gx_button_deselect(button3, false); 
			gx_button_deselect(button4, false); 
			gx_button_deselect(button5, false); 
			gx_button_deselect(button6, false); 
			gx_button_deselect(button7, false); 
		}

MicrosoftTeams-image (2)

Kwon 20 Reputation points

2023-08-22T07:20:59.9133333+00:00

I managed to reduced the influx of inputs to the event queue, however my watchdog pet (in the 100Hz task) highest priority keeps getting triggered when I call gx_widget_show() on a specific widget. After playing with the priorities, I set my buffer thread higher than the GUI thread and what I noticed is that all my windows in the background were being brought the front and getting refreshed and finally the window that I called gx_widget_show() on, is shown. Is there a Z-order variable I can use to check why this is happening?
Ting Zhu 485 Reputation points Microsoft Employee

2023-08-22T08:40:32.6966667+00:00

Have you invoked any GUIX APIs from a thread other than the GUIX system thread? Just want to check if there's a potential scenario where a higher-priority thread is waiting for a resource that's being held by a lower-priority thread.

GUIX widgets are chained based on their Z-order. Drawing occurs sequentially, moving from the first child to the last child, with the last child representing the top widget.
Kwon 20 Reputation points

2023-08-22T22:39:46.7566667+00:00

Yes, I call some events in my state machine. I changed my GUIX system thread to the same highest priority and the system seems to be more responsive.

Here is my window structure

When I call information_subwindow, I see the other windows(device_settings/information/waveforms) being briefly displayed before the information_subwindow shows. When I set the GUIX system thread to the highest priority, There is a ~500ms delay which is most likely caused by the other windows being loaded.
Ting Zhu 485 Reputation points Microsoft Employee

2023-08-23T09:01:19.9566667+00:00

Is the information_subwindow transparent? If so, when this window is marked as dirty for refreshing, the parent window will also refresh within the dirty area. Additionally, if any other sibling windows also overlap the dirty area, they will be subject to refreshing as well.
Kwon 20 Reputation points

2023-08-24T18:17:29.45+00:00

Is there a way to prevent the windows in the background from being refreshed? I removed the transparency option from all my windows and they are still being refreshed.
Ting Zhu 485 Reputation points Microsoft Employee

2023-08-25T08:45:07.33+00:00

Do you use a button to trigger an event to bring a specific subwindow to the front? If the button happens to have a transparent style, clicking on the button would also cause the parent window to refresh in the dirty area. Only a transparent widget would cause its parent to be partially marked as dirty.

Did your subwindows overlap with each other? For example, window A is overlapped with window B, when the parent window is refreshing in the window A area, window B would also be refreshed.

To prevent the windows in the background from being refreshed, you could define a custom draw function for the background window, and draw the desired window as you want.
Kwon 20 Reputation points

2023-08-29T17:37:32.85+00:00

Thank you so much for the help Ting I have gained a lot of progress with your expertise, I will need some time to figure out the custom draw function and let you know the outcomes
LeelaRajeshSayana-MSFT 17,521 Reputation points

2023-09-01T18:22:13.6266667+00:00

Hi @Kwon Greetings! I am checking to see if you need any additional assistance on this question. I highly appreciate it if you can mark the below response as Aceept Answer and Yes so that it would benefit other community members with a similar question find the correct answer. Please let us know if you have any further questions and we would be happy to address them for you.

Accepted answer

0 additional answers

Your answer

LeelaRajeshSayana-MSFT 17,521 Reputation points

2023-08-09T00:36:25.9+00:00

Hi @Kwon Greetings! Welcome to Microsoft Q&A forum. Thank you for posting the question here. Our community SMEs on this this topic will review this question and get back to you with more details as soon as possible. Please stay tuned to this for updates in the next two days.
Kwon 20 Reputation points

2023-08-13T04:49:43.5766667+00:00

We also enabled watchdog and signaled a semaphore to pet the watchdog every 150ms with the reset timeout at 300ms. During a touch event the time between watchdog pets is ~300ms. Somehow the semaphore failed to get and during this time period and the system resets :(
Kwon 20 Reputation points

2023-08-14T19:17:27.4866667+00:00

I found that excessive inputs to the guix event queue causes the system timer thread to not execute, thus introducing delays and preventing the watchdog from getting pet. Is there any configuration to allow GUIX thread to not block other higher priority threads during many inputs?

case GX_SIGNAL(BUTTON, GX_EVENT_TOGGLE_ON): { gx_widget_style_remove(widget1, GX_STYLE_ENABLED); gx_widget_style_remove(widget2, GX_STYLE_ENABLED); gx_widget_style_remove(widget3, GX_STYLE_ENABLED); gx_widget_style_remove(widget4, GX_STYLE_ENABLED); gx_widget_style_remove(widget5, GX_STYLE_ENABLED); gx_widget_style_remove(widget6, GX_STYLE_ENABLED); gx_widget_style_remove(widget7, GX_STYLE_ENABLED); gx_button_deselect(button1, false); gx_button_deselect(button2, false); gx_button_deselect(button3, false); gx_button_deselect(button4, false); gx_button_deselect(button5, false); gx_button_deselect(button6, false); gx_button_deselect(button7, false); }
Kwon 20 Reputation points

2023-08-22T07:20:59.9133333+00:00

I managed to reduced the influx of inputs to the event queue, however my watchdog pet (in the 100Hz task) highest priority keeps getting triggered when I call gx_widget_show() on a specific widget. After playing with the priorities, I set my buffer thread higher than the GUI thread and what I noticed is that all my windows in the background were being brought the front and getting refreshed and finally the window that I called gx_widget_show() on, is shown. Is there a Z-order variable I can use to check why this is happening?
Ting Zhu 485 Reputation points Microsoft Employee

2023-08-22T08:40:32.6966667+00:00

Have you invoked any GUIX APIs from a thread other than the GUIX system thread? Just want to check if there's a potential scenario where a higher-priority thread is waiting for a resource that's being held by a lower-priority thread.

GUIX widgets are chained based on their Z-order. Drawing occurs sequentially, moving from the first child to the last child, with the last child representing the top widget.
Kwon 20 Reputation points

2023-08-22T22:39:46.7566667+00:00

Yes, I call some events in my state machine. I changed my GUIX system thread to the same highest priority and the system seems to be more responsive.

Here is my window structure

When I call information_subwindow, I see the other windows(device_settings/information/waveforms) being briefly displayed before the information_subwindow shows. When I set the GUIX system thread to the highest priority, There is a ~500ms delay which is most likely caused by the other windows being loaded.
Ting Zhu 485 Reputation points Microsoft Employee

2023-08-23T09:01:19.9566667+00:00

Is the information_subwindow transparent? If so, when this window is marked as dirty for refreshing, the parent window will also refresh within the dirty area. Additionally, if any other sibling windows also overlap the dirty area, they will be subject to refreshing as well.
Kwon 20 Reputation points

2023-08-24T18:17:29.45+00:00

Is there a way to prevent the windows in the background from being refreshed? I removed the transparency option from all my windows and they are still being refreshed.
Ting Zhu 485 Reputation points Microsoft Employee

2023-08-25T08:45:07.33+00:00

Do you use a button to trigger an event to bring a specific subwindow to the front? If the button happens to have a transparent style, clicking on the button would also cause the parent window to refresh in the dirty area. Only a transparent widget would cause its parent to be partially marked as dirty.

Did your subwindows overlap with each other? For example, window A is overlapped with window B, when the parent window is refreshing in the window A area, window B would also be refreshed.

To prevent the windows in the background from being refreshed, you could define a custom draw function for the background window, and draw the desired window as you want.
Kwon 20 Reputation points

2023-08-29T17:37:32.85+00:00

Thank you so much for the help Ting I have gained a lot of progress with your expertise, I will need some time to figure out the custom draw function and let you know the outcomes
LeelaRajeshSayana-MSFT 17,521 Reputation points

2023-09-01T18:22:13.6266667+00:00

Hi @Kwon Greetings! I am checking to see if you need any additional assistance on this question. I highly appreciate it if you can mark the below response as Aceept Answer and Yes so that it would benefit other community members with a similar question find the correct answer. Please let us know if you have any further questions and we would be happy to address them for you.

Answer 1

Ting Zhu 485 Microsoft Employee

The system timer has the highest priority, it should not be blocked by the lower-priority GUIX system thread. My assumption is that an abundance of inputs being directed to the GUIX event queue might be causing it to reach its capacity, subsequently leading to the loss of certain timer events.

I suggest reducing the influx of input events and observing if this adjustment restores the proper functionality of the timer.

Share via

How to prevent waveform stuttering when updating prompt widget?

0 additional answers

Your answer