public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ricky Boone <whiplash@planetfurry.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Default Mouse Pointer is Wrong
Date: Wed, 05 Nov 2003 14:33:00 -0000	[thread overview]
Message-ID: <1068042775.32389.26.camel@whiplash.planetfurry.com> (raw)
In-Reply-To: <3FA90473.2050403@msu.edu>

On Wed, 2003-11-05 at 09:08, Harold L Hunt II wrote:
> The default mouse pointer in X is an X.  You are describing the correct 
> scenario.

Okay, my mistake there.  When I am referring to default, I mean the
normal cursor, usually being an arrow. 

> The mouse pointer should not be a Windows arrow.

I didn't think so since it wasn't like that while using the default
cygwin window manager; it was using an arrow.

> The mouse pointer will not be the default pointer that you have under 
> Gnome or KDE on the remote system because you are not running Gnome or 
> KDE on the remote system... you are running only a single application 
> with a local (not remote) window manager (a.k.a. MultiWindow mode, 
> a.k.a. -multiwindow command-line parameter).  Thus, the mouse pointer 
> will be either a) the default mouse pointer (an X), or b) whatever an 
> application sets it to (e.g. a text insertion cursor).
> 
> Does that make sense?  Everything seems to be functioning normally.

It does, but what is preventing the cursor from being displayed as an
arrow like it could without -multiwindow enabled?  Fuctionality-wise it
works just fine, but aesthetically it's not ideal for the user to see an
'X' when they normally see an arrow. 

-- 
Ricky Boone <whiplash@planetfurry.com>
Planetfurry.com


  reply	other threads:[~2003-11-05 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 13:54 Ricky Boone
2003-11-05 14:09 ` Harold L Hunt II
2003-11-05 14:33   ` Ricky Boone [this message]
2003-11-05 14:37 ` Yadin Y. Goldschmidt
2003-11-05 14:59   ` Ricky Boone
2003-11-05 20:42 Cary Jamison
2003-11-05 20:48 ` Harold L Hunt II
2003-11-06 21:42 Cary Jamison

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=1068042775.32389.26.camel@whiplash.planetfurry.com \
    --to=whiplash@planetfurry.com \
    --cc=cygwin-xfree@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).