Here's a summary of changes from README.md:
libX11 version 1.7.0 includes a new API, hence the change from the 1.6
series to 1.7:
* XSetIOErrorExitHandler which provides a mechanism for applications
to recover from I/O error conditions instead of being forced to
exit. Thanks to Carlos Gar
The whole point is a random 3rd party app makes a custom pixmap cursor, and
I was wondering if there is a call to retrieve
the cursor the 3rd party window I have no control over has defined. With
the intention to get the XImage backing it
and copy the pixels.
On Fri, Nov 20, 2020 at 1:11 PM Lucien
Don't you know the ID of your custom pixmap cursors ?
If you do, you can add them to the cases of the switch.
Le 20/11/2020 à 15:22, Ivan Svirid a écrit :
Yea but this does not work with custom pixmap cursors that are not
part of the system cursor theme.
On Fri, Nov 20, 2020 at 7:05 AM Lucien
Yea but this does not work with custom pixmap cursors that are not part of
the system cursor theme.
On Fri, Nov 20, 2020 at 7:05 AM Lucien Gentis <
lucien.gen...@univ-lorraine.fr> wrote:
> In fact, cursor id are defined in cursorfont.h like XC_top_left_corner,
> XC_double_arrow,...
> Le 20/11/202
In fact, cursor id are defined in cursorfont.h like XC_top_left_corner,
XC_double_arrow,...
Le 20/11/2020 à 12:42, Lucien Gentis a écrit :
You can write a function which uses XTestCompareCursor in a switch
which tests known cursor id (top_left_corner, h_double_arrow,...)|
|
Le 19/11/2020 à
You can write a function which uses XTestCompareCursor in a switch which
tests known cursor id (top_left_corner, h_double_arrow,...)|
|
Le 19/11/2020 à 19:59, Ivan Svirid a écrit :
Yea but this only returns true/false it does not return the cursor_id.
On Thu, Nov 19, 2020 at 10:26 AM Lucien Ge
