From kde-core-devel  Sun Nov 24 19:47:30 2002
From: Zack Rusin <zack () kde ! org>
Date: Sun, 24 Nov 2002 19:47:30 +0000
To: kde-core-devel
Subject: Re: XCursor patch
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=103816729027675

On Sunday 24 November 2002 14:31, Fredrik H=F6glund wrote:
> Because with XCreateFontCursor() you only have access to the
> cursors defined in X11/cursorfont.h. Many of the cursors in Qt
> such as the resizing cursors used by KWin aren't available in that
> file, but will be added to the cursor themes. With your patch
> applied Qt won't be able to use them when that happens.
> Without it it will.

Please note that XCreateFontCursor is called only when _not_ a custom=20
cursor is used. Meaning that the custom bitmap cursors are still=20
created as they used to. Only all the default cursors are loaded this=20
way, which is exactly what this patch tries to achieve - make the=20
default cursors Xcursor's.=20

> And making Qt call XCreateFontCursor() is just a hack. You're
> replacing a call to one deprecated function with a call to another.
> Qt should call XcursorLibraryLoadCursor() to load the cursors.

Hmm, that might be why I said in my first email that this is a hack :)=20
The bottom line right now is that using this hack makes KDE use Xcursors=20
and not using it makes KDE display Xcursor's for Xlib and GTK+=20
applications and Qt cursors for KDE application, which looks horribly=20
inconsistent and ugly. I'm, of course, not going to apply it to Qt but=20
for now this is the only solution.

Zack

=2D-=20
"Science is like sex: sometimes something useful comes out,