make the ask bock a reporter

StevenTheSquare

Unecessary. Scratch team should focus on something that can't have a workaround, like layer sensing blocks or making the clones easier to use.

Ihatr

StevenTheSquare wrote:
Unecessary. Scratch team should focus on something that can't have a workaround, like layer sensing blocks or making the clones easier to use.

You say this to every suggestion, try giving a reason instead of just filling the post with WANTS and NEEDS

Maximouse

the2000 wrote:
I don't like this idea because it creates the idea of a reporter block which can pause the script that it's running in. Reporters are supposed to give instant output, not pause like this block does.

The “translate” reporter works like this, and possibly other extension reporters.

gosoccerboy5

Eh.. semi-support. This might confuse some people but on the other hand it makes projects a bit easier to make (but the workaround is albeit easy)

the2000 wrote:
I don't like this idea because it creates the idea of a reporter block which can pause the script that it's running in. Reporters are supposed to give instant output, not pause like this block does.

Yeah, like window.prompt in javascript, input in python, etc..

the2000

gosoccerboy5 wrote:
the2000 wrote:
I don't like this idea because it creates the idea of a reporter block which can pause the script that it's running in. Reporters are supposed to give instant output, not pause like this block does.
Yeah, like window.prompt in javascript, input in python, etc..

I'm talking about Scratch itself though.

Maximouse wrote:
the2000 wrote:
I don't like this idea because it creates the idea of a reporter block which can pause the script that it's running in. Reporters are supposed to give instant output, not pause like this block does.
The “translate” reporter works like this, and possibly other extension reporters.

That's a good point, but I'm pretty sure that the only reporters which do that are ones which need to grab some kind of information from the internet, and those ones only have a very short delay which is mandatory and not a design choice.

DataLabGames

I think this could cause some problems, since the ask and wait block needs a wait. Say if I run the following script and I don't answer immediately, what would happen?

when green flag clicked
say (ask [] and wait)

the2000

DataLabGames wrote:
I think this could cause some problems, since the ask and wait block needs a wait. Say if I run the following script and I don't answer immediately, what would happen?
when green flag clicked
say (ask [] and wait)

The idea is that it would wait for an input before proceeding with the “say” command.

Rendangbike2

DataLabGames wrote:
I think this could cause some problems, since the ask and wait block needs a wait. Say if I run the following script and I don't answer immediately, what would happen?
when green flag clicked
say (ask [] and wait)

It would ask first then the sprite would say the answer, simple.

PkmnQ

the2000 wrote:
I don't like this idea because it creates the idea of a reporter block which can pause the script that it's running in. Reporters are supposed to give instant output, not pause like this block does.

Custom reporters can have wait blocks in them. I guess you have to no support custom reporters now.

define a reporter that waits :: reporter
wait (1) secs
report [:)] :: custom cap

Also, while we're talking about custom reporters,

define ask (input) and wait :: custom reporter
ask (input) and wait
report (answer) :: custom cap

Last edited by PkmnQ (Feb. 22, 2021 01:12:32)

Rendangbike2

Support! If Python most programming languagehas this feature, why not Scratch? And Scratch is supposed to be an introduction to programming so it makes sense.

PkmnQ

By the way, would it still change the answer reporter or no?

Rendangbike2

PkmnQ wrote:
By the way, would it still change the answer reporter or no?

wdym?
bow to me for I am Page the 4th.

Last edited by Rendangbike2 (Feb. 22, 2021 01:50:44)

PkmnQ

Rendangbike2 wrote:
PkmnQ wrote:
By the way, would it still change the answer reporter or no?
wdym?

Would it change this:

(answer)

Rendangbike2

PkmnQ wrote:
Rendangbike2 wrote:
PkmnQ wrote:
By the way, would it still change the answer reporter or no?
wdym?
Would it change this:
(answer)

If you typed in the answer with the (ask [] and wait?), yup.

Steve0Greatness

this is an interesting idea, I do think that it would be nice to shorten code.
I do (sometimes) use multiple ask blocks, but not too often.

the2000

I've changed my mind, this idea is alright I guess. I still think it's a little weird since no other reporter deliberately pauses for this long but eh

fdreerf

mybearworld wrote:
PkmnQ wrote:
I'm assuming that they go from left to right. Support, I think the answer reporter is unnecessary.
Yes, they do.

(ask (ask [Which one executes first, the one on the left, or the one that will make this script work?] and wait ::sensing) and wait ::sensing)

Also, what if I want to use the answer more than once? I'd still need to use a variable to save the answer.

Last edited by fdreerf (Feb. 22, 2021 04:58:59)

PkmnQ

fdreerf wrote:
mybearworld wrote:
PkmnQ wrote:
I'm assuming that they go from left to right. Support, I think the answer reporter is unnecessary.
Yes, they do.
(ask (ask [Which one executes first, the one on the left, or the one that will make this script work?] and wait ::sensing) and wait ::sensing)

Ok, so the order is a bit more complicated. No matter, scratch will decide that.

Last edited by PkmnQ (Feb. 22, 2021 06:03:02)

Steve0Greatness

fdreerf wrote:
mybearworld wrote:
PkmnQ wrote:
I'm assuming that they go from left to right. Support, I think the answer reporter is unnecessary.
Yes, they do.
(ask (ask [Which one executes first, the one on the left, or the one that will make this script work?] and wait ::sensing) and wait ::sensing)
Also, what if I want to use the answer more than once? I'd still need to use a variable to save the answer.

I think that it would ask the one inside first…

mybearworld

fdreerf wrote:
mybearworld wrote:
PkmnQ wrote:
I'm assuming that they go from left to right. Support, I think the answer reporter is unnecessary.
Yes, they do.
(ask (ask [Which one executes first, the one on the left, or the one that will make this script work?] and wait ::sensing) and wait ::sensing)
Also, what if I want to use the answer more than once? I'd still need to use a variable to save the answer.

(join ((2)+(3)) [Which one executes first, the one on the left, or the one that will make this script work?])

Discuss Scratch