Hi,
I would like to ask if there is any way how to prevent unwanted touch events when there is one widget over another, the top widget reacts on touch event by closing itself and the bottom widget still "receives" touch and fires its own event.
As an example, I have a bgr window with listview, and an error dialog with confirmation button. Something happens, I show the dialog and when the button is pressed, dialog is closed AND the item in the listview at the touch location is selected.
Basically I am looking for something similar to button widget's REACT_ON_LEVEL = 1 functionality for other widgets. In other words, touch should be processed only once. After it triggers some event on the dialog and that dialog is closed, it should not be processed any further until the touch is released.
Is there any way how to achieve this in emWin? I am not using emWin touch drivers, so touch events are passed to emWin by GUI_TOUCH_StoreStateEx. The behavior I described could be achieved by filtering the touch events on my side, but I would rather use some built-in principle if available.
Thanks
Petr
I would like to ask if there is any way how to prevent unwanted touch events when there is one widget over another, the top widget reacts on touch event by closing itself and the bottom widget still "receives" touch and fires its own event.
As an example, I have a bgr window with listview, and an error dialog with confirmation button. Something happens, I show the dialog and when the button is pressed, dialog is closed AND the item in the listview at the touch location is selected.
Basically I am looking for something similar to button widget's REACT_ON_LEVEL = 1 functionality for other widgets. In other words, touch should be processed only once. After it triggers some event on the dialog and that dialog is closed, it should not be processed any further until the touch is released.
Is there any way how to achieve this in emWin? I am not using emWin touch drivers, so touch events are passed to emWin by GUI_TOUCH_StoreStateEx. The behavior I described could be achieved by filtering the touch events on my side, but I would rather use some built-in principle if available.
Thanks
Petr