I am attempting to work around a bug in the Wayland / Xlib interface.
Specifically, the Wayland developers abandoned Xlib [XWarpPointer()] functionality that my application (REX, imagtek.com) uses heavily.
In a nutshell, this broke my application.
Attempts to resolve this issue on the gitlab portal devolved into infantile accusations of 'insensitivity' from me, with the final result that my bug report and request to preserve specific Xlib functionality was erased as an act of spite.
Interface design that is hostage to juvenile parsing of language seeking offense bodes a dark future for LINUX.
Removing functionality from a 30 year old interface because the person using it pissed you off, is idiotic.
People need to grow up and look past their precious feelings to larger issues that are in play, or LINUX is toast.
Just my opinion.
Specifically, the Wayland developers abandoned Xlib [XWarpPointer()] functionality that my application (REX, imagtek.com) uses heavily.
In a nutshell, this broke my application.
Attempts to resolve this issue on the gitlab portal devolved into infantile accusations of 'insensitivity' from me, with the final result that my bug report and request to preserve specific Xlib functionality was erased as an act of spite.
Interface design that is hostage to juvenile parsing of language seeking offense bodes a dark future for LINUX.
Removing functionality from a 30 year old interface because the person using it pissed you off, is idiotic.
People need to grow up and look past their precious feelings to larger issues that are in play, or LINUX is toast.
Just my opinion.