Android Question How to avoid using "Wait For"

[LucaMs]

I would like to avoid forcing the user of my class to use "WAIT FOR" while waiting for a class routine to finish moving a View.

Example (Duration, SomeView, ... fake stuff, only as example)

' clsMyClass
Public Sub Move
   SomeView.SetLayoutAnimated(Duration, 100, ...)
End Sub

I wish the user-developer could write like this:

objMyClass.Move
Log("Done") ' <--- this line executed only after Duration ms

And not like:

Wait For (objMyClass.Move) Complete(Unused As Boolean)
Log("Done") ' <--- this line executed only after Duration ms

 

[Erel]

No such thing.

If the user wants that the code will wait for something to complete then they need to use Wait For.

 

[LucaMs]

No such thing.

If the user wants that the code will wait for something to complete then they need to use Wait For.

I suspected it.
Also begin to suspect that you see while I am writing the question, because I did not have time to post it that you had already answered ?

 

[josejad]

Also begin to suspect that you see while I am writing the question, because I did not have time to post it that you had already answered

I have thought it too a couple of times.

 

[agraham]

wish the user-developer could write like this:

No such thing.

For clarification, the reason it is not possible is that for Wait For to work the sub-routine call stack has to be totally unwound back to the message loop, which means that every call has to return. So your objMyClass.Move has to return or it will block and not let the message loop process the wait.

 

[AnandGupta]

No such thing.

This I think is due to ASynchronization logic of Android.

@LucaMs , I think, you want is Synchronization logic, like old msgbox logic.

Regards,

Anand

 

[Erel]

This I think is due to ASynchronization logic of Android.

Nope. It has nothing to do with Android. The resumable subs feature is a 100% B4X compiler feature.

 

[AnandGupta]

The resumable subs feature is a 100% B4X compiler feature.

So, Lucas can put the 'wait for' in his class itself (maybe with some parameter) and compiler will work.
No need for 'wait for' in calling program .

Regards,

Anand

 

[Cableguy]

Nope. It has nothing to do with Android. The resumable subs feature is a 100% B4X compiler feature.

So this means that no other language that targets Android has this feature ??

 

[agraham]

So, Lucas can put the 'wait for' in his class itself (maybe with some parameter) and compiler will work.
No need for 'wait for' in calling program .

Wrong, I'm afraid. As Erel said it won't work. Read my post #5 above.

 

[Erel]

So, Lucas can put the 'wait for' in his class itself (maybe with some parameter) and compiler will work.
No need for 'wait for' in calling program .

Nope. The developer must call the resumable sub with Wait For, otherwise the developer code will not wait for the class method to complete.

As I said, you must use Wait For if you want the execution to wait for something. There is no other (good) option.

So this means that no other language that targets Android has this feature ??

.Net - Xamarin includes a similar feature (async / await). It is not exactly the same and it doesn't work with events.

 

[agraham]

So this means that no other language that targets Android has this feature ??

Xamarin (C#) has a similar await statement but the impementation is totally different as C# has the ability to save and resume executiom contexts whereas (as far as I know) Java doesn't.