LOOPER v2 not working correctly when started from step enter trigger

[ta-aoki]

I just imported LOOPER v2 https://library.tulip.co/apps/looper to my sandbox instance, and created simple test App which just iterate through “a”, “b”, and “c”.

I am expecting to see “0:a”, “1:b”, “2:c” when the loop runs.
I do see that when I start the loop by pressing the button.
However, I see “0:a”, “1:a”, “2:c” when I start the loop from step enter trigger (by setting the Begin loop flag to Yes).

Why is it not working as expected?

Tulip

[thorsten.langner]

I guess this fix might help

Looper v2 - looping the list two times

I might oversee something but, I guess the fix for the code is as simple as that: [image] Just add the highlighted check. The issue is, when the widget is loaded, it will check for the start boolean (and starts the loop, if true) AND checks the iteration (and starts the loop, if not undefined or null). So if the start boolean is true and the iteration is 0, both will trigger the start of the loop. When adding the iteration beeing >0 this should only trigger the start once.

if not, some screenshots of the setup would help.

[ta-aoki]

Thank you! It fixed the problem.
Please release LOOPER v3 with this fix.

[Beth]

Great timing for this question, we are in the process of releasing an updated looper widget with this fix! I will follow up here once we do. Should be coming shortly

[ta-aoki]

I now have this issue about custom widget which is also related to LOOPER v2.1.

SetValue does not have effect immediately?

Because of this behavior, we cannot rely on this line 7 in LOOPER v2.1 to have the “Iteration” initialized to 0. We need make sure the prop “Iteration” is initialized to 0 in the app side before changing the “Begin Loop” prop to Yes. [image]

Could Tulip please check whether this is expected behavior?

[ta-aoki]

@Beth @thorsten.langner
Please try this simple test App starting the looper v2.1 from the step enter trigger.
app.json (13.9 KB)
I wanted to see “A”, “B”, “C” appear, but I see “{}” instead of “A”.

I am guessing that this happens because SetValue is not having immediate effect.

[Mihaly]

Thank you for pointing out the issue with the behavior of the Looper widget — you’re absolutely right, it was not functioning as expected. We’ve identified and fixed the problem, and the updated version will be available in the Tulip Library starting this Thursday, June 19.

In the meantime, we recommend checking out the following updated guide on unit testing the Looper widget, which may help you validate its behavior in your environment:
Looper Unit Test

We really appreciate your feedback — insights like this help us improve the reliability and usefulness of widgets for the entire community.

[ta-aoki]

Thank you!
This Thursday …June right? Perfect!

Please could you comment on this post too?

SetValue does not have effect immediately?

I have this simple CustomWidget. Why do I see unexpected values for N even though setValue was called just before getValue? [image] HTML <div id="mainblock"> <div id="log_display">NO LOG YET</div> </div> JavaScript "use strict"; let log = []; function add_log(str) { log.push(`[${new Date(Date.now()).toLocaleTimeString()}]${str}`); document.querySelector("#log_display").innerText = log.join("\n"); } getValue("B", (value) => { if (value == true) { setValue("N", 0); add_log(`…

[ta-aoki]

@Mihaly

Thursday, June 19.

Where can I download/install the new Looper v3 ?
I went through Tulip library and knowledge base, but I couldn’t find the available link.

[ta-aoki]

@Mihaly
I was able to download Looper v3 from the library. I will check how it works.

On the other hand, I guess this link on the Knowledge Base need to be updated. Please check.

Looper Unit Test

[ta-aoki]

I guess you need to rewrite this yellow part to v3.

[ta-aoki]

The link is now fixed. Thank you.

[ta-aoki]

This seems to be now fixed. Thank you.

[ta-aoki]

I tested Looper v3.
Now it is working as expected. I see “A”, “B”, “C” appear correctly.

I read through the difference between v2.1 and v3 code.
It seems like adding “+0” to the v2.1 code will solve the issue I oberved.

Thank you.

[ta-aoki]

@Mihaly
I found a problem in LOOPER v3. Please run this simple test App.
app.json (14.9 KB)

If you go to step2, I was expecting to see “A”, “B”, “C”, but I see “B”, “B”, “C”.

This happens if the “Iteration” prop is 1 before starting the loop.

As I explained in this post,

SetValue does not have effect immediately?

Because of this behavior, we cannot rely on this line 7 in LOOPER v2.1 to have the “Iteration” initialized to 0. We need make sure the prop “Iteration” is initialized to 0 in the app side before changing the “Begin Loop” prop to Yes. [image]

setValue("Iteration", 0);

does not work as a initializer.

I propose do something like

if(0 != getValue("Iteration")){
   fireEvent("Error", "Iteration not zero");
   return;
}

here, so that the loop do not start if the Iteration is not zero.

[thorsten.langner]

A While ago I posted this fix for looper v2

For me that works and I never had any issues…

---

find here:

Looper v2 - looping the list two times

I might oversee something but, I guess the fix for the code is as simple as that: [image] Just add the highlighted check. The issue is, when the widget is loaded, it will check for the start boolean (and starts the loop, if true) AND checks the iteration (and starts the loop, if not undefined or null). So if the start boolean is true and the iteration is 0, both will trigger the start of the loop. When adding the iteration beeing >0 this should only trigger the start once.

[ta-aoki]

Thank you for the comment.

Yes I know that. LOOPER v3 already have that implemented.

However, I still see this “B”->“B”->“C” issue.
This happens when “Iteration” was not zero when “Begin Loop” became true.
It happens because the initializer “setValue(“Iteration”, 0);” is having the effect asynchronously.

[thorsten.langner]

I’m sorry. I can’t test your application, because I can not import your json.

do you mind sharing screenshots of the trigger logic, leading to this behaviour?

[ta-aoki]

I am sorry, I did not explain enough how to import that json file.
Could you please follow this procedure

1. Create zip file with one single “app.json” in it.
2. Rename the zip file to “looper_v3_test_counter_starting_from_1.zip”
3. Import the zip file from the App folder

[ta-aoki]

This is the screenshot.

Variables.

Props

“begin loop” trigger on step2 enter