On Nov 04, 2006, at 12:07 AM, Rubber Chicken Software Co. wrote:
At 03:28 PM 11/2/2006, you wrote:
If your callback function is updating the UI somehow, more likely
is that the window
simply isn't redrawing until the dylib function returns.
And you are correct! I finally figured to put a App.DoEvents in the
callback routine, and things seems A OK.
However, the docs do say that DoEvents shouldn't be used in a GUI
app, saying it will lead to instability. Will it in this case?
There's only three things happening. A StaticText gets updated, a
ProgressBar is updated, and if a button gets pressed in the RB
interface, the callback returns false to the dylib, causing a Cancel.
App.DoEvents causes the main thread of RB to be run again and it
_could_ lead to instability.
UI updates happen when this occurs.
It's not certain to, but I dont think there's anyone that can say "If
you do X it WILL 100% for sure cause problems by using App.DoEvents"
If your dylib could Yield time back to RB then you would not have
this issue.
But, it can only do that if it's a plugin and calls the provided
function.
_______________________________________________
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>
