could you elaborate more? i’m not sure i understand…
i think he means that you can add rules for ‘when clone 1 of self is tapped’, ‘when clone 2 of square is not pressed’, etc
oooh yes! we need this for variables too!
also, the ‘requests’ tag is for commission and request topics but i don’t think you’ll need to remove it.
What about a;
When (Self) is tapped <
. Check once if [Clone index = 1 or whatever clone you want]
. Whatever you want it to do
That’s actually already possible, i said it wasn’t (a mistake).
Just use when self is tapped: check once if self clone index=(clonenumber) then, the code.
Yeah that’s what I said. /lh /nm
So is your suggestion resolved then?
wo, no, this isn’t solved - sls’s code will only run for the clone that is being pressed, not any other clone. and cutekcat’s suggestion is when a specific clone is tapped, another unrelated clone will run the code in the tapped magenta rule.
Yes that’s true, they still give out the same result though but it could lead to a bit of lag. This is a way to somewhat workaround this though.
Like this? Access Clone Attributes
I read it wrong, I thought you meant making it so a specific clone would do something when tapped. But you might be able to work around this with the Broadcast Message block.
Yeah I wish that was possible
I would like the feature to move with your FINGERS except for blocks on the Hopscotch Web Explorer(I do not have an IOS device😥)
I do really LOVE that feature!