nanogui: Mouse pointer does not change in FLTK + nxlib + nano-X
Subject:
RE: [nanogui] Mouse pointer does not change in FLTK + nxlib + nano-X
From:
"Martin Kajdas" ####@####.####
Date:
24 Feb 2006 18:35:15 +0000
Message-Id: <CF2BB830A62F914F848E5AD5FFF57AC22914DE@mkmail.MKPROD.COM>
That explains the problem and it is a problem.
Because this is the way the X-windows operates, the nxlib should be the one keeping the cursor count and nano-X should not be changed in any way (if possible).
The question is when to call GrDestroyCursor, keeping the number of clients using this cursor and destroy it when the number falls to 0.
In my case (FLTK app), every XFreeCursor call is followed by XDefineCursor at some time later when needed.
I will try to save the 'cursor' value in XFreeCursor and call the GrDestroyCursor in XDefineCursor when the previous 'cursor' is marked to be deleted.
This may be enough for me.
Martin
-----Original Message-----
From: Greg Haerr ####@####.####
Sent: Friday, February 24, 2006 9:58 AM
To: Martin Kajdas; ####@####.####
Subject: Re: [nanogui] Mouse pointer does not change in FLTK + nxlib + nano-X
> The question is: how to fix XFreeCrusor() properly so that the cursors are
eventually destroyed (GrDestroyCrusor call in XFreeCursor)
Sounds like X keeps a cursor count, and then frees
when 0. We free immediately in any case.
You might have to keep an NXLIB cursor count, although
this could be problematic since we don't keep
an internal cursor count in nano-X. The internal
function GsCheckCursor looks up the window cursor
for display, and if not, uses the standard cursor.
I'd recommend starting with an external cursor count
before changing nano-X internals, since keeping a
cursor count in nano-X changes semantics for other
nano-X programs.
Regards,
Greg
