public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Frank Eske <fne.bugzilla@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin X server accepts xfixes version 5.0 but doesn't handle xcb_xfixes_hide_cursor
Date: Thu, 15 Oct 2020 15:31:55 -0400	[thread overview]
Message-ID: <CAETRzVJAZ1706umKnnLLJuCg5kDRRFaE98fO87UFqRksUSQKDg@mail.gmail.com> (raw)

I'm building an XCB-based application that uses xcb_xfixes_hide_cursor. The
X server reports back version 5.0 in xcb_fixes_query_version_reply and
accepts xcb_xfixes_hide_cursor requests, but does not hide the cursor. When
omitting the xcb_fixes_query_version operation, the xcb_xfixes_hide_cursor
is (properly) rejected. Compiling and running the same program under
Fedora, the cursor is hidden when running natively. When running an ssh
remote xterm to Fedora, the hide_cursor again does nothing.

The associated X11/extensions/Xfixes.h XFixesHideCursor() works
identically. It fails to do anything but does not report any error
indication.

When testing this on Fedora, I also noticed that xterm hides the cursor in
exactly the same manner I want for my application, and doesn't on Cygwin
(where it always remains visible.) That is, typing hides the cursor and
cursor movement shows it again. This should eliminate the need for a test
case which, because of all the ancillary setup needed, would be quite large.

Possibly the simplest fix would be to properly report back the version of
Xfixes you actually support, document that restriction at least in the
include file, and reject the Xfixes extension requests you don't handle. As
an aside, almost every other X feature I've tried to use has worked
identically on Cygwin and Fedora, usage bugs included.

Note that there is probably a work-around for this missing function by
creating a blank cursor and using that instead of hide_cursor.

             reply	other threads:[~2020-10-15 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 19:31 Frank Eske [this message]
2020-10-25 16:20 ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAETRzVJAZ1706umKnnLLJuCg5kDRRFaE98fO87UFqRksUSQKDg@mail.gmail.com \
    --to=fne.bugzilla@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).