Define block replaces upvar when ring glitches

[sunnyandshivcodebros]

This bug happened on my iPad while I didn’t have internet. (Safari) I put

(this [script v])

into

define ((block)) [block] (()$>)

and it glitched and made

define ((block)) [block] (this [script V])

I ran it and it produced this.

define ((this [script V] :: control)) [block] (this [script V])

I can’t reproduce this, so I don’t have a video.

[sathvikrias]

Yeah, there was already a topic about this, although I don’t remember if it was resolved. I’m struggling to find the link but I swear it’s here somewhere, I think @d016 might have been in the topic?

[sunnyandshivcodebros]

also, the upvar block got forced out of the upvar slot??? and it still acted like an upvar

[d016]

Yeah, I remember making a topic like that

[sunnyandshivcodebros]

found it

Define (block) [] (this [script v])

This isn’t a very high priority, but… [Untitled script pic (81)] causes issues: [Untitled script pic (82)] (the “block” reporter thinks it’s an upvar)

[sunnyandshivcodebros]

replicated it

[askofep1]

it can also happen on accident.
A slight work around would be to type in a random sequence of characters and hope no one uses the variable name.
Each character needs to be entered in with some sort of alt code equivalent for the operating system or a copy paste trick.

[sunnyandshivcodebros]

I made the original post because it happened on accident. i didnt unringify it, i just dropped the this script in and it self-unringified

[askofep1]

I tried to fix it but they said no

[mark4sisb]

…Because you made an unsolicited PR with no context or clear explanation of testing.

@jens

what is this about? Does this address / fix the issue of using this script unringified as function argument in the define block that y’all have been glossing over in the forum? If so I have questions:

1. Why don’t you write readable, explicit, verbose (using full sentences, you know) bug reports instead of posting a single picture?
2. Why don’t you even tell me here what this is about? Just issuing a PR does not help, I can’t read your mind
3. Which tests did you conduct to make sure your proposed changes don’t affect any other use cases? Any?
4. Does this change actually address all the situations, or just the first one you’ve stumbled upon?
5. What’s the use case you’re hoping for? In other words, it seems incredibly stupid to even want to use this script inside the function arg slot of the define block. Are you just trying to fix something that happens by mistake - but it can’t, right, because you have to go out of your way to unringify the function arg, so you’re definitely looking for trouble when you do that -

@sunnyandshivcodebros

i just dropped the this script in and it self-unringified

I can’t reproduce this. Presumably this was a one-off glitch in your iPad. But it does suggest that this can happen accidentally. And if you’re not careful playing around with it, you can break things so much that you have to enter dev mode and manually delete the offending morphs to continue coding. From what I can tell, however, this has been at least partly fixed, as it only occurs if the name of the upvar is the same as the name of the block you are defining.

PS: You can make the “this script” be in the control category with :: in SnapBlocks (and the menu read-only via capital “V”).
define ((this [script V] :: control)) [block] (this [script V])
define ((this [script V] :: control)) [block] (this [script V])

[sunnyandshivcodebros]

ohhh i kept using single colons instead of double colons, so that’s why it didnt work

[askofep1]

old

its not dev mode

you can put a for loop with an upvar named “block” in a define block and it happens

you can ringify the upvar with a this [script V] and move it out

dusty gif

[redgeographysnap]

@askofep1

its not dev mode

you can put a for loop with an upvar named “block” in a define block and it happens

He was talking about removing the THIS SCRIPT upvar