Home »
Public Forums »
archive »
Re: BOX_CURSOR
| Re: BOX_CURSOR [message #7387] |
Wed, 06 November 1996 00:00 |
Robert Moss
Messages: 74
Registered: February 1996
|
Member |
|
|
Mario Noyon wrote:
>
> 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
This is not a bug. It's simply queueing up the button events to be
processed after the BOX_CURSOR routine is finished. The solution is
to disable the button events from the draw widget while BOX_CURSOR
is active:
widget_control, draw_wid_id, sensitive = 0
box_cursor.....
widget_control, draw_wid_id, sensitive = 1
--
Robert M. Moss, Ph.D. - mossrm@texaco.com - FAX (713)954-6911
------------------------------------------------------------ -----
This does not necessarily reflect the opinions of Texaco Inc.
|
|
|
|
Current Time: Wed Oct 08 13:40:24 PDT 2025
Total time taken to generate the page: 0.00531 seconds
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
