bf83ff3fbd
The X11 event loop in the POSIX simulator was processing MotionNotify (touch/mouse movement)and ButtonPress/ButtonRelease events unconditionally, even when the touchscreen feature(CONFIG_SIM_TOUCHSCREEN) was disabled. This could lead to unnecessary event processing, potential compiler warnings about unusedfunctions (e.g., sim_buttonevent), or unintended behavior in simulator builds withouttouchscreen support. The touchscreen-related event handling should only be active whenthe corresponding configuration is enabled. This fix wraps the MotionNotify and ButtonPress/ButtonRelease event handling logicwith #ifdef CONFIG_SIM_TOUCHSCREEN guards to: 1. Ensure touchscreen/mouse event processing is only compiled when CONFIG_SIM_TOUCHSCREEN is enabled. 2. Eliminate unused code warnings in non-touchscreen simulator builds. 3. Align event loop behavior with the configured feature set, reducing unnecessary runtime overhead. The change maintains full touchscreen functionality when the config is enabled, whilecleaning up the code path for builds that don't require touchscreen support. Signed-off-by: chao an <anchao.archer@bytedance.com> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.