BOX_CURSOR [message #7397] |
Tue, 05 November 1996 00:00  |
Mario Noyon
Messages: 11 Registered: August 1996
|
Junior Member |
|
|
I would like to know if anyone has met this problem before and if it's a
bug :
I have a drawable widget that consider button_events. So when I click
in his widget the event A is called.
But I want to use the procedure BOX_CURSOR with another button. Then
when the user click on this button BOX_CURSOR is called. Every thing
happens well but when the user exits off the procedure BOX_CURSOR, as he
has clicked to move his BOX and to exit the procedure the event A is
called.
That does not happen all the time and it is not vey convenient.
Thanks for those who can help me (the others also...)
--
NOYON Mario
Computer Science in Medical imaging
University of Bordeaux 2
mnoyon@jmc-luni.u-bordeaux2.fr
|
|
|
Re: BOX_CURSOR [message #35837 is a reply to message #7397] |
Thu, 31 July 2003 19:11  |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
michela writes:
> I am using box_cursor to select a box in a larger image. The problem
> is that if the image I displayed shows large pixel-to-pixel variation
> (like for example ima=randomu(seed,500,500))
> the box that box_cursor plots on the image is invisible.
> I tried to change the color of the box by changing the color table,
> but it does not work
> Someone can give me a suggestion?
Don't use Box_Cursor. :-)
Box_Cursor uses an "XOR" technique. What you
want is a "Device Copy" technique. Look, for
example, at how this is done in ZIMAGE, which
allows you to draw a box (of a particular color)
in a image to create a zoom region.
http://www.dfanning.com/zimage.pro
And here is an article that describes the
"Device Copy" technique in some detail:
http://www.dfanning.com/widget_tips/rubberband_widget.html
Cheers,
David
--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|