Jari Vetoniemi
Jari Vetoniemi
What if you move wlc_input_terminate before wlc_compositor_release in wlc.c @ wlc_cleanup? Does this happen under X11 backend?
What is exact trace for this? As that track is missing important symbols. If this is under X11 the proper fix is to have the terminating order corrected in compositor.c.
A) wlc would need to support this. B) We could open wayland internals more, we already pretty much expose libinput and xkb to keep simple.
Weston implements on-screen keyboards too. It might be useful to see how they solved it.
For approach B), https://github.com/Cloudef/wlc/blob/feature/wayland-extensions/include/wlc/wlc-wayland.h could include function that returns input resources for view. From there on you can do anything wayland-server.h allows.
#71 somewhat related.
In wlc, needs support in orbment.
The configuration still has some issues (mainly keybindings), and thus isn't documented well (the default ini backend anyways). However to change prefix, create $XDG_CONFIG_HOME/orbment/orbment.ini and use contents: ``` [keybindings] #...
Just adding some older examples and resources. https://ptpb.pw/cAf7/ini (Sample ini) https://github.com/Cloudef/orbment/issues/89#issuecomment-136092559 (Example of input configuration) In future the configurable keys will be exposed more conventietly (At least printed on log...
The reason is that the pixels are written as uint32 per pixel, so in little endian it's reversed.