A long time ago, Erel created a post about how to handle multiple events that were constantly triggered and showing only the last value, i know its vague but i have spent some time already looking for it on google and here in the forum.
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Android Question Missing Erel's tutorial
- Thread starter EnriqueGonzalez
- Start date
- Similar Threads Similar Threads
Solution
Dam* found it.
The index pattern.
www.b4x.com
It was resumable sub. Thanks @aeric
The index pattern.
[B4X] Resumable subs and the index pattern
The "index pattern" is a pattern that you can see in many examples and libraries where resumable subs are used. It is a simple solution to avoid race conditions and unexpected states. The resumable subs code like all other standard B4X code, is executed by the main thread. Still, with resumable...
www.b4x.com
It was resumable sub. Thanks @aeric
Not sure, as RS only receive one event, and this tutorial was about a single sub handling multiple events
Upvote
0
It was a gif, or a simple video not like the Venmo ones. May be the buttons example could be, I remember having a global variable keeping the index of the events
Upvote
0
No, I saw that one, it is like the opposite, letting the events flow and just selecting the last one
Upvote
0
Dam* found it.
The index pattern.
www.b4x.com
It was resumable sub. Thanks @aeric
The index pattern.
[B4X] Resumable subs and the index pattern
The "index pattern" is a pattern that you can see in many examples and libraries where resumable subs are used. It is a simple solution to avoid race conditions and unexpected states. The resumable subs code like all other standard B4X code, is executed by the main thread. Still, with resumable...
www.b4x.com
It was resumable sub. Thanks @aeric
Upvote
1
Solution
