Search Results

DoeEvents is not synonymous with Sleep(0). They have different behaviour. DoEvents is synchronous and pumps the message loop before proceeding with the following code. Sleep(0) is asynchronous and returns from the Sub to the message loop immediately and the following code is scheduled to run at a la

Starting from B4A v7.0 the following warning will appear for DoEvents calls: DoEvents is deprecated. It can lead to stability issues. Use Sleep(0) instead (if really needed). The purpose of DoEvents was to allow the UI to be updated while the main thread is busy. DoEvents which shares the same impl
link: Existing libraries will continue to work as DoEvents is still available. If your code uses Wait For and you compile it to a library then it will only
link: 1) You can do everything that you like in the resumable sub, including modifying lists or maps or global variables, except of calling Return <value he
link: I had use Doevents to show the rotate of Progressdialog. strquery = "SELECT * FROM tabella " dbcursor = Main.dbSql.ExecQuery(strquery) Dim doc

DoEvents is the opposite of the new sleep feature. It holds the main thread in a loop (while processing the message loop). The new sleep feature is much more sophisticated and it doesn't hold the main thread. It instead stores the current context and later resumes it. Anyway, As DonManfred wrote th

we are talking about a wait loop here, in this case it's bad. in other cases like filling a large select list the doevents is a solution to prevent "app not responding" notifications. but in general wait loops are to be avoided when you have timers available.
link: add DoEvents to your loop so that it gets the time to update the screen. that approach is bad, you better use a timer instead.
link: You're almost right. In this case it is not only a wait like this Erel's routine: Sub WaitFor(Milliseconds As Int) Dim s As Long s = DateTime.Now Do

https://www.b4x..png DoEvents DoEvents is deprecated. It can lead to stability issues. Consider using Sleep(0) instead.

(warning #10) GenerateForms - 4071: DoEvents is deprecated. It can lead to stability issues. Use Sleep(0) instead (if really needed). (warning #33) GenerateForms - 4073: DoEvents is deprecated. It can lead to stability issues. Use Sleep(0) instead (if really needed). (warning #33) GenerateForms - 41

You should try the DoEvents and see what happens. DoEvents Processes waiting messages in the messages queue. DoEvents can be called inside lengthy loops to allow the program to update its UI.
link: Did you try to add a DoEvents when you populate the list like this to see if it helps? For i=0 To Cursor1.RowCount-1 Cursor1.Position = i lst.Add(
link: SQL.ExecQueryAsync did not do the job DoEvent is much better I also reduced the list size by better executing query Thanks

First step is to check the actual task and see whether it can be optimized or be done asynchronously. Please post the relevant code.
link: Threading. But just find where in your loop there is most long code and use Sleep(0). Now it looks that you use Sleep(0) in wrong point.
link: I saw a recommendation not to use DoEvents: Source: https://www.b4x.-alternative.68918/#post-437288 But the window freezes if you don't use someth

As in another post .... DoEvents is a no-no in Android 4.4 ! It causes app to behave erratically as processes start/end at non-user controlled times. Avoid at all cost ... use Tick event.

I'm not so sure. That DoEvents is inside of innerRestoreState routine, which is a recursive routine (it calls itself). It is also called by a public method, RestoreState, and we cannot know how the user-developer will call this routine (he could call it at bottom of a "calling chain") So: 1) I t
link: Replace DoEvents with sleep(0) ?
link: Hello, I've replaced DoEvents with Sleep (with Replace all ....), and get problems. (I do not remember exactly what, but I think the app has crashed)
link: Is there a way to remove DoEvents from StateManager Class?

Powered by ColBERT