thedougnutcookiepie wrote:

Hoi people just asking im new so when u ask a question how do u make it so the answer triggers another thing to happen?

DadOfMrLog wrote:

thedougnutcookiepie wrote:

Hoi people just asking im new so when u ask a question how do u make it so the answer triggers another thing to happen?

I think your question isn't related to this discussion thread (even though it is about the ask block). –I'd recommend you start a new discussion thread with your question.

Also, this discussion thread is very old – in fact, it's out of date now.

However, for the sake of completeness for this discussion (and before it gets closed), I'll note that it's now possible to remove an ask-and-wait prompt by stopping its script from another script via the “stop other scripts in sprite” block.

Alternatively, if the ask-and-wait is being run by a clone, then deleting the clone will also remove its ask prompt.

Both of the above features were added to Scratch since the posts before the last recent one in this thread. (Here's the commit on github that made the appropriate changes to the Scratch 2.0 source code: https://github.com/LLK/scratch-flash/pull/950 ).

I'll now report this discussion to be closed, since there isn't really anything left to add to it.

Harakou wrote:

This does seem mostly solved, though using a stop other scripts block could be clunky in some situations. I think that's the best solution and will probably remain so, but it might be worth hearing ideas on how to improve that all the same.

• "stop [other scripts in sprite v]" to stop the asking script (a touch annoying if you have other scripts in the sprite/clone that are currently running, and you'd rather not stop them too);

• use a clone to ask, and delete the asking clone to cancel (means you need a new clone set aside specifically for the asking);

• put the ask-and-wait in a broadcast receiver script, and re-send the broadcast to cancel it, without the receiver script asking this time (not intuitive at all, but probably the least ‘intrusive’ method to put into an existing project, once you understand how the method works);

• a new “asking script” item in the "stop […v]“ block's menu – i.e. ”stop [asking script v]" (which is not immediately obvious where to find it, since it's nowhere near the other ask-related blocks, though OK once you know about it);

• a “stop asking” block (or “cancel asking”) in the light-blue sensors block palette (which has a potential problem with the resulting “answer” if the asking script continues executing the blocks that come after the cancelled “ask and wait” block);

• a built-in cancel button which leads to some predetermined string for the “answer” that means the ask-and-wait was cancelled, e.g. “<CANCELLED>” (which clearly has a problem if that string could be one you might want to allow to be typed into the ask prompt).

DadOfMrLog wrote:

Harakou wrote:

This does seem mostly solved, though using a stop other scripts block could be clunky in some situations. I think that's the best solution and will probably remain so, but it might be worth hearing ideas on how to improve that all the same.

I guess it's possible there could be some alternative ideas, other than the current three working methods (I'm ignoring my original “stop all” method, since that's so poor…):

• "stop [other scripts in sprite v]" to stop the asking script (a touch annoying if you have other scripts in the sprite/clone that are currently running, and you'd rather not stop them too);

• use a clone to ask, and delete the asking clone to cancel (means you need a new clone set aside specifically for the asking);

• put the ask-and-wait in a broadcast receiver script, and re-send the broadcast to cancel it, without the receiver script asking this time (not intuitive at all, but probably the least ‘intrusive’ method to put into an existing project, once you understand how the method works);

…and the three main (currently unimplemented) suggestions mentioned in previous posts of this discussion thread:

• a new “asking script” item in the "stop […v]“ block's menu – i.e. ”stop [asking script v]" (which is not immediately obvious where to find it, since it's nowhere near the other ask-related blocks, though OK once you know about it);

• a “stop asking” block (or “cancel asking”) in the light-blue sensors block palette (which has a potential problem with the resulting “answer” if the asking script continues executing the blocks that come after the cancelled “ask and wait” block);

• a built-in cancel button which leads to some predetermined string for the “answer” that means the ask-and-wait was cancelled, e.g. “<CANCELLED>” (which clearly has a problem if that string could be one you might want to allow to be typed into the ask prompt).

Any other suggestions…?

braxbroscratcher wrote:

DadOfMrLog wrote:

…[blah blah]…

Any other suggestions…?

A cancel block that puts an untypable character in as the return value.

After whatever is before this :: events hat
ask [What's your name?] :: sensing stack // This is a new block
if <key [space] pressed?> then
stop asking :: sensing stack // Same here
end

stop [ v]

Zekrom01 wrote:

Enter a null answer, no support

Also, I found a workaround here

Nambaseking01 wrote:

Tunde123 wrote:

Nambaseking01 wrote:

Tunde123 wrote:

-Brandon_Boy- wrote:

This is stupid

Please do not necropost.

Necroposting is allowed in the “Suggestions” forum. This topic is also linked to as a reference on the Scratch Wiki page you sent, so it's confirmed by the Scratch Team.

Yeah but they are supposed to add to the topic also, which is what they aren't doing.

Oh, alright. Yes, I also noticed that, but since you specifically said “necroposting”, I was a bit confused. No issues, I see your point.

LeDerpy123 wrote:

As sonicklye said, what would happen? Would the script just stop? Thank wouldn't be very useful. Would it keep going? What would it do then? Would the answer string be blank or would it say something like “answer cancelled”? There are too many possibilities for what would happen. So sorry, no support.

stop asking and [end script v] :: sensing
stop asking and [continue script v] :: sensing

mozarty wrote:

There should SERIOUSLY be a cancel button when a sprite asks you a question (

ask [] and wait

). It's really annoying.

stop asking