home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!newsgate.watson.ibm.com!yktnews!admin!ghostwind!shmdgljd
- From: shmdgljd@rchland.vnet.ibm.com (Jay Schmidgall)
- Subject: Re: Finding the current cursor
- Sender: news@rchland.ibm.com
- Message-ID: <1992Jul23.141226.19607@rchland.ibm.com>
- Date: Thu, 23 Jul 1992 14:12:26 GMT
- Reply-To: jay@vnet.ibm.com
- Disclaimer: This posting represents the poster's views, not necessarily those of IBM
- References: <1992Jul22.161928.19371@andersen.co.uk>
- Nntp-Posting-Host: ghostwind.rchland.ibm.com
- Organization: IBM Rochester, MN
- Lines: 14
-
- In article <1992Jul22.161928.19371@andersen.co.uk>, you write:
- |> During an application I need to change the cursor, I do this with
- |> XdefineCursor. I would like to be able to store the original cursor so
- |> that I can change it back. I have tried to retrieve the cursor with
- |> XtSetArg and XtGetValues with a resource of XmRCursor but this does not
- |> work.
-
- I don't think you need to store the original cursor at all; instead, store
- your new cursor. Then, when you're done, undefine the new cursor. The
- original cursor is automagically restored.
-
- --
- : jay jay@vnet.ibm.com My opinions and ideas, not my employer's.
- : shmdgljd@rchland.vnet.ibm.com (c) Copyright 1992. All rights reserved.
-