aboutsummaryrefslogtreecommitdiff
path: root/nx-X11/extras/Mesa.patches_6.4.2/series
diff options
context:
space:
mode:
authorMihai Moldovan <ionic@ionic.de>2017-09-13 11:50:40 +0200
committerMihai Moldovan <ionic@ionic.de>2017-09-13 11:50:43 +0200
commit0815fb06f1135f6f276d2d534a569e6b10b52241 (patch)
treefa8c74256f2a51568a92c0510e7fae6acaed3c15 /nx-X11/extras/Mesa.patches_6.4.2/series
parent81569ad6b58d51cc2691f075d70f89fe470a48eb (diff)
downloadnx-libs-0815fb06f1135f6f276d2d534a569e6b10b52241.tar.gz
nx-libs-0815fb06f1135f6f276d2d534a569e6b10b52241.tar.bz2
nx-libs-0815fb06f1135f6f276d2d534a569e6b10b52241.zip
nx-X11/programs/Xserver/hw/nxagent/Render.c: use macros obtaining values from _XPrivDisplay instead of the other Display structure directly.
Fixes: ArcticaProject/nx-libs#512 It's unclear to me why (Display*)(dpy)->bitmap_pad and (_XPrivDisplay)(dpy)->bitmap_pad produce different results. Technically, Display is referencing the _XDisplay/Display structure defined in Xlibint.h, while _XPrivDisplay is a typedef'd pointer to the (anonymous) structure defined in Xlib.h, since we're not defining the XLIB_ILLEGAL_ACCESS macro. The weird part is that both should be equal when it comes to its bitmap_pad, byte_order and bitmap_bit_order members.
Diffstat (limited to 'nx-X11/extras/Mesa.patches_6.4.2/series')
0 files changed, 0 insertions, 0 deletions