On Nov 4, 2006, at 8:30 AM, Alfred Van Hoek wrote:
On Nov 4, 2006, at 3:08 AM, Norman Palardy wrote:
OK, now, found the (probable) solution. Just added a App.DoEvents
call and everything seems to update properly. Evidentially the
callback couldn't update the windows with their changes without
it. I hope that's not an unstable thing to do.
Why not make this a plugin that can then send an event back to RB ?
It's not hard with David Addey's XCode starter and may let you
then call back safely and reliably
No, it will lead to the same problem, and a thread won't work
either. It is a callback that expects you to return immediately. So
your thinking should be different. Return from the callback
immediately, don't do anything in that callback, other then telling
your code that you were called by the dylib. At the main event loop
you then should react with AddressOF or a REALevent.
Start thinking...
And DoEvents is not the solution, you are forcing the main event loop
to cycle, which could lead to re-entrant problems.
_______________________________________________
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>
