On 9-Jan-07, at 7:48 PM, Tom Benson wrote:
James,
Just out of curiosity, if you flip the windows asynchronous window
attribute to be on, does the timer still not fire until you let go
of the mouse??
This code should make window events fire (and timers and threads
within the window) continue to fire even with the mouse down. I'm
not sure if the windows execution is interrupted still a control
receives the event, but if the window receives the event (click,
drag, whatever) then I can verify that this works fine from within
RB 5.5.5 and up.
Cheers,
Tom Benson
Declare Function ChangeWindowAttributes Lib "Carbon" (window as
WindowPtr, setTheseAttributes as Integer, clearTheseAttributes as
Integer) as Integer
if b then
If GesaltLib.IsPanther() Then
call ChangeWindowAttributes(w, 8388608, 0) //asynchronous on
else
call ChangeWindowAttributes(w, 0, 8388608) //asynchronous off
end
End If
All this switch does is allow stuff to run while dragging the window
around. You can manipulate canvases and the window directly without
affecting timers even without this switch, but standard RB controls
will block in both cases. Also note that RB windows break in a few
other ways when using that attribute. I have an AsyncDragWindow class
available that avoids these problems: <http://
developer.chaoticbox.com/realbasic_classes.php>
Frank.
<http://developer.chaoticbox.com/>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
