At 05:45 PM 10/10/2006, you wrote:
> Now I get a StackOverflowException in that callback function.
> Any ideas on the reason why?
RB is not thread safe.
Yuck, that's fairly awful.
Can you suggest anything to help with the core problem, which is
getting an interface element (like a text box or similar) to update
on the screen as a result of a callback WHILE a function is waiting
for a dylib to return?
Chronologically, it seems to be like this:
Call dylib function
Callback 1 comes in, adds a row to a listbox
Callback 2 comes in, adds a row to a listbox
Callback 3 comes in, adds a row to a listbox
...
dylib returns
Rows get added
I'm not sure if the callbacks get called before the return or after
the return of the dylib function. If before, then it's something in
RB that could be programmed to force updating of the screen? If
after, then what are some suggestions on how to get them coming in before?
Garth Hjelte
Sampler User
_______________________________________________
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>
