Ideas as to why this might happen?
How can you “step into” it?
Clear as mud, right?
[code]method blah(Message as text)
// process the Message
select case xxx
// set up some timers
// set up other timers
The reason I mention the timers is that seems to be the only significant change between the 2 cases; the rest is simply command generation.
If youre using a Timer as opposed to a WebTimer, that could be the cause as the Action event fires on the main thread.
Also, I meant Xojo version 2007 r2.1, not r1 above.
if Greg is right about the timer vs webTimer, and it certainly sounds to me like that is likely the case not withstanding the Xojo version or if its a web project or not, I can say for sure that you need to get the proper session context setup for the control.
I just put something like this somewhere before accessing the controls properties:
Dim Context As New WebSessionContext( app.SessionForControl( Me))
assuming that Me is the control youre talking to, otherwise put the control reference there.
This is somewhat voodoo in my mind as you dont have to actually do anything with the context object once you fetch it, the act of having one in scope is enough to make it work. There are examples of that in the web documentation as well I believe.
Or… perhaps you are talking about something totally different In which case the above will not be helpful at all
Its never safe to set text in a control from the main thread. It may seem to work in debug mode, but thats only because you have only one session. When live, itll be sent to whichever session currently has an event in progress.