On 30/6/05 at 18:27, Valentin Schmidt <[EMAIL PROTECTED]> wrote: > thanx for the info. A workaround would be to let the callback create a > timeout object (see code below which does succesfully throw an error). > So, I wonder, maybe it would be a good habit to ALWAYS use > 1ms-timout-objects for xtra callbacks? What do you think?
That could work. I ended up just storing the list returned in a property and adding an extra state to my state machine, which did the right thing with the list, then moved on. Works fine. It's more a question of knowing that the issue is there because it's tricky to catch a silent error! Various workarounds can be imagined. Thanks Alex, for the info about MUI. Does this mean it applies to all Xtras that have a callback mechanism? Brennan [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
