| Re: CURSOR and draw widgets [message #20755] |
Thu, 20 July 2000 00:00 |
David Bowman
Messages: 10
Registered: July 2000
|
Junior Member |
|
|
Thanks... I should have been able to figure that one out... A
clear-cut case of being too close to the problem, too late in the day!
:-)
regards,
david
In article <3977309A.5A8CA7DA@ssec.wisc.edu>, Liam E.Gumley
<Liam.Gumley@ssec.wisc.edu> wrote:
>
> Have you considered using CONVERT_COORD to covert device coordinates to
> data (or normal) coordinates?
>
> Cheers,
> Liam.
> http://cimss.ssec.wisc.edu/~gumley
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-=
David Bowman "Smash forehead on keyboard to continue."
Laboratoire Tectonique
Institut de Physique du Globe - Paris
4 Place Jussieu
75252 Paris Cedex 05
France
|
|
|
|
| Re: CURSOR and draw widgets [message #20756 is a reply to message #20755] |
Thu, 20 July 2000 00:00  |
Liam E. Gumley
Messages: 378
Registered: January 2000
|
Senior Member |
|
|
David Bowman wrote:
> Is there any simple way to get the cursor position from a draw
> widget in DATA coordinates? For some reason that I don't comprehend,
> one is not supposed to use the CURSOR routine with widgets, however
> button and tracking events only give device coordinates.
Have you considered using CONVERT_COORD to covert device coordinates to
data (or normal) coordinates?
Cheers,
Liam.
http://cimss.ssec.wisc.edu/~gumley
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
