Acfboy commented on PR #3624: URL: https://github.com/apache/nuttx-apps/pull/3624#issuecomment-5036344138
> The NnuttX provides its KEYCODE_xxx macros in [kbd_codec.h](https://github.com/apache/nuttx/blob/master/include/nuttx/input/kbd_codec.h#L44) for special keys. But only for these and rest is expected to be ASCII. Hi, @ppisa . I have a question about this statement. It seems to me that the ranges of the `KEYCODE_xxx` macros and ASCII are conflicting, which makes it impossible for my driver to distinguish whether it's a character or a special key. In my `sim:mw` setup, this results in being unable to type a space. > I think that there could be two drivers, one for event type and another for raw keyboards. This could be configured through Kconfig, same would be useful for device name. Two drivers makes the code cleaner. But specify the device path/name via Kconfig risks inconsistency with the real device. Alternatively, if Microwindows auto-selects the device based on NuttX config, then we have to keep both sides in sync — which adds maintenance overhead. > You should try even if Nano-X server and clients can be run on NuttX. Okay, I'll try server and client of NanoX. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
