Use this template to make awesome bug reports:
Your username: Tri-Angle Strudios
What kind of device are you using?: (Also include iOS version, and Hopscotch version) iPad 6th gen iPadOS15 Hopscotch newest version
1 sentence description of the problem (I was doing _________, and then __________ happened): I was doing comparaisons with local variables + magentas containers and it didnt not work as expected
Steps that the Hopscotch team can take to reproduce my problem every time:
I expected this to happen: All are moving
But instead this happened: Top one is not moving
Here’s a sweet screenshot:
this only happens with clones, the original objects are doing their job correctly
Oh yeah that still happens… I think it’s related to this too
sorry, but i dont see how it can be related
that was a fast tag lol t1
I did mean to make a bug report for this on the forum, but hadn’t gotten around to it yet, so thanks for reporting it!
I linked the wrong project, whoops. It could be the same thing where the scope of the variable is being lost, but I meant to link this one
hey @t1_hopscotch, will this be fixed soon? I can write a whole essay and list down every situation where this bug is preventing people from coding correctly if you feel this isn’t as important as other bugs :)
Haha I definitely get your frustration there — it is pretty common to use local variables and use the Whens with them.
It’s an important bug to fix, but it’s not just me deciding though — we just unfortunately hadn’t been able to prioritise some of the more difficult webplayer bugs for a while. There is a temporary workaround with this one with the Check Once If, but I agree that it is confusing if you are just trying to use the local variables in the Whens at first.
But I’m hoping we’re able to address some of them soon in the next webplayer update or two (by the end of the year)
ignore me then, this is no longer a priority (imo an urgent bug is a bug that it’s impossible to get a workaround)