ppisa commented on PR #3624:
URL: https://github.com/apache/nuttx-apps/pull/3624#issuecomment-5036088397

   Yes, this what I have proposed and expect as well.
   
   You should set something like `SCREEN=NUTTX` or `SCREEN=NUTTX_FB` in the 
local `graphics/microwindows/Makefile` and then Microwindows with merged code 
should add correct driver sources when you include 
`microwindows/src/drivers/Objects.rules`.
   
   Same for the `MOUSE` and `KEYBOARD`. The question is if the mouse should be 
a single driver or one for relative motion mouse device and other for 
touchscreen.
   
   As for the keyboard, there can be space to think how to map it the best way. 
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. 
Microwindows works with `MWKEY` and `MWSCANCODE` which aligns with concept of 
real X11 where the keyboards provide "position" of pressed key by scancode and 
it can be remapped to symbol even latter in application. But usually `MWKEY` 
code is used and its definitions are provided in 
[src/include/mwtypes.h](https://github.com/ghaerr/microwindows/blob/master/src/include/mwtypes.h#L1402).
   
   You provide translation in `translate_keycode` when keyboard is in 
`g_kbd_mode` set to `KBD_MODE_EVENT` but there is heuristics during open. 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. So it is necessary to think a little what is the best option there.
   
   You should try even if Nano-X server and clients can be run on NuttX. I do 
not see X11 graphics option as the main priority, but it would prove that even 
complex setup can be build and check if it is stable on NuttX. 
   
   
   
   


-- 
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]

Reply via email to