Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GX_VERTICAL_LIST does not release input if it contains GX_SINGLE_LINE_TEXT_INPUT #83

Closed
maxim-lbmv opened this issue Dec 3, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@maxim-lbmv
Copy link

Describe the bug
GX_VERTICAL_LIST does not release input if it contains GX_SINGLE_LINE_TEXT_INPUT

This happens because after clicking on GX_SINGLE_LINE_TEXT_INPUT it takes the input and receives the GX_EVENT_PEN_UP event, which should have taken the input from GX_SINGLE_LINE_TEXT_INPUT. As a result, clicks are processed by GX_VERTICAL_LIST and other elements cannot receive focus.

Please also mention any information which could help others to understand
the problem you're facing:

  • What target device are you using? Cortex M7
  • Which version of Azure RTOS? 6.1
  • What toolchain and environment? IAR
  • What have you tried to diagnose or workaround this issue? We have to add parents for GX_SINGLE_LINE_TEXT_INPUT located in GX_VERTICAL_LIST that block the GX_EVENT_PEN_DOWN event from passing to GX_VERTICAL_LIST so that it does not capture the input.

To Reproduce
Steps to reproduce the behavior:

  1. Create a project with GX_VERTICAL_LIST containing GX_SINGLE_LINE_TEXT_INPUT and another widget
  2. Click on GX_SINGLE_LINE_TEXT_INPUT
  3. Click on another widget

Expected behavior
The click event will be handled by another widget

Impact
Click events are handled by GX_VERTICAL_LIST

Logs and console output
No

Additional context
No

@maxim-lbmv maxim-lbmv added the bug Something isn't working label Dec 3, 2023
@ting-ms
Copy link
Contributor

ting-ms commented Dec 7, 2023

@maxim-lbmv Thank you for your feedback! We can reproduce the issue and we'll fix it in the future.

@ting-ms
Copy link
Contributor

ting-ms commented Dec 18, 2023

@maxim-lbmv This issue has been fixed in this PR: #91

@ting-ms ting-ms closed this as completed Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants