Alright so putting false in an ask (): block does nothing:
ask {<false>} and wait //Does not do anything.
why do you need to do this?
I don’t… But bugs are bugs, right?
I’m pretty sure it’s not a bug
yeah, I guess. usually I try to only report the things that are really worth the developer’s time just because he has so much to do. You didn’t do anything wrong though.
You can just ringify it. And why will anyone need to ask false?
ask-ing false or a nullish value (an empty input slot, zero) has semantics in Snap!: It lets you abort processes that currently either actively ask the user something or that queue up to later ask the user something. In short: ask[false] closes any currently active prompter and un-blocks all processes queued up for prompting.
i like that you can use false to unblock any ASK blocks but the empty input slot one is a little annoying. i would usually have a question or some ui to display what i wanted the user to type in but now some of my old projects are broken and simply dont ask for input anymore. is there some way to restore old functionality to older projects?
Yeah, there should be a
stop asking ::sensing
Block or something.
For now, use a zero-width character like the zero width joiner.
the problem is i dont feel like going through the dozens of old projects that do that. since they changed it ive started adding messages to the ask block
You can get the old behaviour by immediately clearing the speech bubble (the wait 0 secs block tells Snap to yield and initialize the launched thread - this way, the next time the script yields (from the ask block) the say [ ] will be ready to run):
We can then modify the primitive definition of the ask block to use this:
Simply import this block as an image (as shown above) or XML file into all affected projects and it will be fixed (note that I could have used anything, not just a space character, in the first ask block).
that’s really clever!