public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygwin-xfree@cygwin.com Subject: Re: Default Mouse Pointer is Wrong Date: Wed, 05 Nov 2003 20:48:00 -0000 [thread overview] Message-ID: <3FA96216.70706@msu.edu> (raw) In-Reply-To: <C19DFD46D76FE24A9C2A98DEEB8E226905E808@pqorexmain.powerquest.pq> Cary Jamison wrote: > "Ricky Boone" <whiplash@planetfurry.com> wrote in message > news:<1068044377.32617.1.camel@whiplash.planetfurry.com>... > >>On Wed, 2003-11-05 at 09:37, Yadin Y. Goldschmidt wrote: >> >>>Colin Harrison suggested long time ago to add the following line to > > the end > >>>of your startxwin.bat file: >>>xsetroot -cursor_name left_ptr -fg white -bg black >>>This will change the default mouse from an x to a white arrow. >> >>Ah ha, that did the trick. My apologies, I didn't even notice the >>suggestion when I searched for it. -.-;; >> >>Thanks for the help. :) > > > I've noticed this too, but haven't complained about it. I didn't > realize the problem was specific to the -multiwindow window manager. This isn't a problem. It is "the way it works". > If this is true, than -multiwindow is not behaving as expected nor as > other window managers behave wrt default cursors. The xsetroot is a > work-around, but it seems to me this should be regarded as a bug in the > window manager. The 'X' should be the default cursor when over the root > window but an arrow when over an application window. Since -multiwindow > doesn't really have a visible root window, it seems like permanently > changing the default cursor to a pointer would be a good/quick solution. Fine. Run 'twm' as your window manager. Doesn't it do the same exact thing? That is the way that I have been reading the emails... if that is not the case, then could somebody please describe this better.? The solution you propose is not trivial. That is why this is "the way it works" and not a bug. I'm sure that upon further inspection you would figure out that trying to change this policy would result in the creation of a mouse-cursor over-riding policy that is a lot more complicated than what you think it would be. I'm pretty sure that it would be complicated enough that it isn't worth looking into. Of course, feel free to code me into submission. Harold
next prev parent reply other threads:[~2003-11-05 20:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-05 20:42 Cary Jamison 2003-11-05 20:48 ` Harold L Hunt II [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-11-06 21:42 Cary Jamison 2003-11-05 13:54 Ricky Boone 2003-11-05 14:09 ` Harold L Hunt II 2003-11-05 14:33 ` Ricky Boone 2003-11-05 14:37 ` Yadin Y. Goldschmidt 2003-11-05 14:59 ` Ricky Boone
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=3FA96216.70706@msu.edu \ --to=huntharo@msu.edu \ --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: linkBe 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).