Kevin Well-Known Member Licensed User Longtime User May 13, 2012 #1 Erel (or whoever else knows): I was wondering if you could please explain in somewhat simple terms what the DoEvents issue is or how that statement can produce an error or crash. I seem to be confused as to how that statement got mixed in with the recycle twice thing, unless I have missed some other threads or posts. My concern is that I published an app update today that added a bunch of DoEvents statements to see if it helps with some ANR freezes I've seen in my dev console. Most of these statements were inserted into For...Next loops that process lists and listviews.
Erel (or whoever else knows): I was wondering if you could please explain in somewhat simple terms what the DoEvents issue is or how that statement can produce an error or crash. I seem to be confused as to how that statement got mixed in with the recycle twice thing, unless I have missed some other threads or posts. My concern is that I published an app update today that added a bunch of DoEvents statements to see if it helps with some ANR freezes I've seen in my dev console. Most of these statements were inserted into For...Next loops that process lists and listviews.
Erel B4X founder Staff member Licensed User Longtime User May 13, 2012 #2 There is an issue with Android 4.0.3 and Android 4.0.4 where a Msgbox or DoEvents call (or debugger breakpoint) inside Touch event or Button_Up / Button_Down events crashes the application. Basic4android v1.92 will soon be released with a fix to this issue. Probably next week.
There is an issue with Android 4.0.3 and Android 4.0.4 where a Msgbox or DoEvents call (or debugger breakpoint) inside Touch event or Button_Up / Button_Down events crashes the application. Basic4android v1.92 will soon be released with a fix to this issue. Probably next week.
Kevin Well-Known Member Licensed User Longtime User May 13, 2012 #3 Thanks for the clarification. Will the update also address the MsgBox problem as well, or just DoEvents? Can this happen if we only use Button_Click events or does it specifically have to be an Up or Down event with the MsgBox or DoEvents in it?
Thanks for the clarification. Will the update also address the MsgBox problem as well, or just DoEvents? Can this happen if we only use Button_Click events or does it specifically have to be an Up or Down event with the MsgBox or DoEvents in it?
Erel B4X founder Staff member Licensed User Longtime User May 13, 2012 #4 Will the update also address the MsgBox problem as well, or just DoEvents? Click to expand... It should fix all issues. Can this happen if we only use Button_Click events Click to expand... No.
Will the update also address the MsgBox problem as well, or just DoEvents? Click to expand... It should fix all issues. Can this happen if we only use Button_Click events Click to expand... No.
Kevin Well-Known Member Licensed User Longtime User May 13, 2012 #5 Thanks again for the further clarification. I'm not at home to check my code right now but I'm pretty sure I don't use Up or Down events for anything in my app. Click and Changed mostly.
Thanks again for the further clarification. I'm not at home to check my code right now but I'm pretty sure I don't use Up or Down events for anything in my app. Click and Changed mostly.
