comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Can Timer interrupt widget callbacks?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Can Timer interrupt widget callbacks? [message #90699 is a reply to message #90698] Sun, 29 March 2015 11:58 Go to previous messageGo to previous message
Helder Marchetto is currently offline  Helder Marchetto
Messages: 520
Registered: November 2011
Senior Member
On Sunday, March 29, 2015 at 2:45:33 PM UTC+2, David Grier wrote:
> Dear Folks,
>
> A change in the behavior of Timer callbacks from IDL 8.3 to IDL 8.4 has broken one of my
> applications, and I could use some help in fixing it.
>
> Under IDL 8.3, the firing of an asynchronous Timer preempts widget callbacks.
> This behavior appears to have been reversed in IDL 8.4, so that callbacks now take precedence.
>
> Here's the issue ...
>
> My application has a widget_draw object that is supposed to update at regular intervals while
> the user drags graphics objects across the screen. I'm using Timer events to trigger the updates.
> Under IDL 8.3, the widget_draw's animation is smooth. Under IDL 8.4, the animation stops
> updating during drag events, which defeats the purpose of the animation.
>
> Is there any way to restore the old behavior so that firing a Timer interrupts a widget
> callback, perhaps as an option to Timer::Set()?
>
> If there's no way to make the Timer "dominant", does anyone have suggestions for modifying
> my widget callbacks so that they can check for pending timer events and handle them?
>
> All the best,
>
> David

Hi David,
not sure if this is what you are looking for... could it be: !DEBUG_PROCESS_EVENTS = 0

From the IDL help (http://www.exelisvis.com/docs/Whats_New_8_3.html):
Event handling while debugging
In the past, IDL would not sent widget events when you were stopped within a routine. Now, by default, IDL sends widget events even when stopped within a routine. This allows you to use graphics and widget applications while debugging.
There is a new system variable, !DEBUG_PROCESS_EVENTS, that can be set to 0 to disable this behavior, or to 1 to enable this behavior. The default value is 1.

I hope it helps.

Cheers,
Helder
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Save data in hdf with Projection Information
Next Topic: Rebin or interpolate to resample data

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:46:48 PDT 2025

Total time taken to generate the page: 0.00474 seconds