dvargasews wrote:

The loop won't be possible until custom reporters are added.

My other idea about making blocks available once workarounds have been provided fits that.

And by the way, without this block or a workaround, the Scratch project that I want to make would be practically impossible.

theonlygusti wrote:

dvargasews wrote:

The loop won't be possible until custom reporters are added.

My other idea about making blocks available once workarounds have been provided fits that.

And by the way, without this block or a workaround, the Scratch project that I want to make would be practically impossible.

There are loads of workarounds.

But yes, this block needs to be added.

dvargasews wrote:

because each workaround has its own unique problems.

theonlygusti wrote:

dvargasews wrote:

because each workaround has its own unique problems.

They don't. Lots of the workaround posted in this so far do have problems, but its easy enough to create a viable workaround to this block.

dvargasews wrote:

theonlygusti wrote:

dvargasews wrote:

because each workaround has its own unique problems.

They don't. Lots of the workaround posted in this so far do have problems, but its easy enough to create a viable workaround to this block.

I don't want to take any chances.

jromagnoli wrote:

dvargasews wrote:

theonlygusti wrote:

dvargasews wrote:

because each workaround has its own unique problems.

They don't. Lots of the workaround posted in this so far do have problems, but its easy enough to create a viable workaround to this block.

I don't want to take any chances.

Yes, and the “workaround” is harder to use than the proposed block.

Cub56 wrote:

Semi-support, but this is workaroundable by having each character add to a list (add letter 1 to list, add letter 2 to list etc) and then a kind of loop counter variable that does something like this:

set [i v] to [1]
repeat (length of (list :: list))
set [variable v] to (join [(variable)] (item (i) v) of [list v] :: list))
change [i v] by (1)
end

set [i v] to [1]
repeat (length of (list :: list))
set [variable v] to (join [(variable)] (item (i) of [list v] :: list)
change [i v] by (1)
end

Tymewalk wrote:

Full support. This is a real pain in the neck every time you have to make these huge, clunky blocks.

dvargasews wrote:

The loop won't be possible until custom reporters are added.

My other idea about making blocks available once workarounds have been provided fits that.

And by the way, without this block or a workaround, the Scratch project that I want to make would be practically impossible.

jellyrmaker wrote:

man, on scratch 3.0 there have custom reporter! Why they should add an thing if you can make this at final of this year?

dvargasews wrote:

jellyrmaker wrote:

man, on scratch 3.0 there have custom reporter! Why they should add an thing if you can make this at final of this year?

Scratch 3.0 won't be coming out until January 2019 at earliest.

ZZ9PluralZAlpha wrote:

I thought it was sometime this year.

Sigton wrote:

ZZ9PluralZAlpha wrote:

I thought it was sometime this year.

The alpha will hopefully be done by the end of the year, but the finished release won't be until later.

Sigton

ZZ9PluralZAlpha wrote:

dvargasews wrote:

jellyrmaker wrote:

man, on scratch 3.0 there have custom reporter! Why they should add an thing if you can make this at final of this year?

Scratch 3.0 won't be coming out until January 2019 at earliest.

I thought it was sometime this year.

dvargasews wrote:

ZZ9PluralZAlpha wrote:

dvargasews wrote:

jellyrmaker wrote:

man, on scratch 3.0 there have custom reporter! Why they should add an thing if you can make this at final of this year?

Scratch 3.0 won't be coming out until January 2019 at earliest.

I thought it was sometime this year.

I thought that I read in a forum post that I think was by one of the ACMs a few weeks or months back that Scratch 3.0 would be finished in 2019 at earliest.

dvargasews wrote:

ZZ9PluralZAlpha wrote:

dvargasews wrote:

jellyrmaker wrote:

man, on scratch 3.0 there have custom reporter! Why they should add an thing if you can make this at final of this year?

Scratch 3.0 won't be coming out until January 2019 at earliest.

I thought it was sometime this year.

I thought that I read in a forum post that I think was by one of the ACMs a few weeks or months back that Scratch 3.0 would be finished in 2019 at earliest.