You know what. I may be wrong here. Your interaction may be related to the way you’re using composer.* so strike that last post.
I will take a look. Just a bit thanks.
You know what. I may be wrong here. Your interaction may be related to the way you’re using composer.* so strike that last post.
I will take a look. Just a bit thanks.
I’m sorry again, I hope this simple example can be analyzed and given a solution.
sorry my English.
OK. I’ve looked AT THE ORIGINAL POSTED CODE and I can see that you have some bad behavior, but I don’t know where it is coming from.
Things I noticed:
Sorry, I could’t figure it out. This is why I ask for super simple tiny demos. There is just too much code to penetrate.
My best guess is that you’re staring the timer multiple times and not properly canceling them since you only have the handle to the last timer you started.
Ok, I’ll see if I can debug these timers.
Hi again.
I looked at your newer code. I cleaned it up a bit and modified it.
Compare what I’m doing to your code.
That Cool! Thanks a lot, although the code changed seems a little complicated (I am a beginner) I was happy that my problem was solved even with a little more code.
I’ll take a look at the modifications to see if I learn!
Thank you very much
Yeah…sorry about that.
I made those changes because your original method had a number of best-practices issues that would have caused no end of problems:
Also, you were using timers and transitions in a sub-optimal way.
My unified single transition + onComplete listener approach is shorter and safer. That said, it is more technical, so I understand if it seems confusing at first.