Variable Passing Bug
Posted: 18 Sep 2017 14:16
Automagic 1.34.0 has a new bug in variable passing when there is list or map element access. This is the flow to test the bug.
The bug is : If there is a variable referring to any list or map elements just like c or d, then any variable declared in the same script won't appear in the elements after it.
You can try it to check at script 3, tap the variable and there is no b, c or d. The b, c, d also got red underlined, means the variables are not available. Strange thing is they all appear in debug dialog. So the variables are there, they simply disappear from selection. e also produce a proper list from b,c,d.
If in script 2, we comment out the c and d line, and uncomment the one that refer directly to the whole list and map (c = list and d = map), then b, c, d appear properly at script 3.
I tried at both my phone LP 5.1, 1.34.0, and both give same bug. Don't if everyone have the same problem. Tested in another LP 5.1 phone, with 1.33.0 installed, the bug doesn't appear. The b, c, d can be found at variable in script 3, even at script 2 refer to list/map element.
The bug is not fatal, but simply annoying. Because when compacting the flow I just curious why the variables are red underlined, even though I have properly declared it in the previous element and connect them. It slows down debugging process, since usually red underlined means undeclared/unavailable variables, which is usually the error.
The flow consist of 3 script and 1 debug dialog. In script 1, just variable init. Second script is where the problem lies. I have b assigned to string, c to list[0] and d to map["second"]The bug is : If there is a variable referring to any list or map elements just like c or d, then any variable declared in the same script won't appear in the elements after it.
You can try it to check at script 3, tap the variable and there is no b, c or d. The b, c, d also got red underlined, means the variables are not available. Strange thing is they all appear in debug dialog. So the variables are there, they simply disappear from selection. e also produce a proper list from b,c,d.
If in script 2, we comment out the c and d line, and uncomment the one that refer directly to the whole list and map (c = list and d = map), then b, c, d appear properly at script 3.
I tried at both my phone LP 5.1, 1.34.0, and both give same bug. Don't if everyone have the same problem. Tested in another LP 5.1 phone, with 1.33.0 installed, the bug doesn't appear. The b, c, d can be found at variable in script 3, even at script 2 refer to list/map element.
The bug is not fatal, but simply annoying. Because when compacting the flow I just curious why the variables are red underlined, even though I have properly declared it in the previous element and connect them. It slows down debugging process, since usually red underlined means undeclared/unavailable variables, which is usually the error.