The reason has to do with those threads I talked about above. Jon_Ogden: For Each activeSession As WebSession In App.Sessions Which is the best way to do it or doesn’t it matter? I’m thinking the second but thought I’d ask here… Where w.ProcessData would basically contain:ĭataListbox.DeleteAllRows For i as integer = 0 to MyData.Ubound Is it better instead to process all your data and then call a client side method for each session that manipulates the user interface elements in the browser? So it would be something like: For Each activeSession As WebSession In App.Sessions
Xojo pagewithname code#
I’m thinking there’s a chance that when you start looking at the RowCount the code in all the browser sessions may not have executed or executed fully - correct? Does Xojo wait for each method client side to complete or is calling a client side method kind of like starting a new thread that runs independently? I know that the DeleteAllRows method will complete BEFORE I start looking at the RowCount value of the Listbox in the For/Next loop.īut how does it do it in the Web app? If I do this on a Server Side routine: For Each activeSession As WebSession In App.SessionsĭIm w as Web = Web(ActiveSession.PageWithName("Web", True)) So in a desktop app, if I have code like: DataListbox.DeleteAllRows I’m curious about how user interface elements in the browser are updated in web apps.
0 kommentar(er)
