Maximouse wrote:

the2000 wrote:

I'm assuming that the OP doesn't want the useless hidden blocks like ([sound name v]) to be added to the main palette.

It isn't completely useless (the “start sound” block actually has it as an input) but it wouldn't make sense to add it to the palette.

Wouldn't that just do the same thing as selecting the sound manually though? Unless you mean that this block is the result of some kind of internal quirk.

the2000 wrote:

Wouldn't that just do the same thing as selecting the sound manually though? Unless you mean that this block is the result of some kind of internal quirk.

It exists because of how Blockly (and thus Scratch) handles block inputs. There are two types of inputs: value inputs, into which you can drag reporters, and fields (text/number inputs, dropdowns), which let you select a value but don't accept reporters. But because most blocks need fields that do accept reporters, shadow blocks exist: these are reporters that can't be dragged around. For example, in the

start sound [meow v] :: sound

block, the dropdown input is actually a shadow reporter block (sound_sounds_menu).

Edit: the Blockly documentation for shadow blocks can be found here.

Maximouse wrote:

the2000 wrote:

Wouldn't that just do the same thing as selecting the sound manually though? Unless you mean that this block is the result of some kind of internal quirk.

It exists because of how Blockly (and thus Scratch) handles block inputs. There are two types of inputs: value inputs, into which you can drag reporters, and fields (text/number inputs, dropdowns), which let you select a value but don't accept reporters. But because most blocks need fields that do accept reporter, shadow blocks exist: these are reporters that can't be dragged around. For example, in the

start sound [meow v] :: sound

block, the dropdown input is actually a shadow reporter block (sound_sounds_menu).

Ah, but the ::sound block is using the same shadow reporter sourcecode?

PS Your post got cited.

dhfbei8987 wrote:

Ah, but the [sound v]::sound block is using the same shadow reporter sourcecode?

(Square brackets disappear in the forums because the parser thinks they're markup, I edited the quote to fix that)
It's the same block as the input to start sound, but without the shadow property, so it behaves like a normal block.

dhfbei8987 wrote:

PS Your post got cited.

Interesting.

Support, I'd love to see new blocks. JSON stuff is complicated and I don't understand it, I would be so happy if these hidden blocks were added.

bump

And if anyone's wondering what they are

what hidden blocks are there?

ham07 wrote:

what hidden blocks are there?

Look at the post above yours

DualPikachu wrote:

And if anyone's wondering what they are

Some of those hidden blocks such as all at once do not work anymore, actually if you've used snap, there is a block called warp, which acts like all at once. The loops such as for and while do work still, but im not so sure about the counter block.

ThatExplosivePigeon wrote:

DualPikachu wrote:

And if anyone's wondering what they are
-snip-

Some of those hidden blocks such as all at once do not work anymore, actually if you've used snap, there is a block called warp, which acts like all at once. The loops such as for and while do work still, but im not so sure about the counter block.

I know.
Also, please snip long quotes.

i agree, adding some of them would be great yet some ,such as all at once, is best staying out of scratch.

ham07 wrote:

i agree, adding some of them would be great yet some ,such as all at once, is best staying out of scratch.

All at once has some uses, in snap and other ones, but run without screen refresh, has completely destroyed it. I agree with you, lets not add that one back.

ThatExplosivePigeon wrote:

ham07 wrote:

i agree, adding some of them would be great yet some ,such as all at once, is best staying out of scratch.

All at once has some uses, in snap and other ones, but run without screen refresh, has completely destroyed it. I agree with you, lets not add that one back.

I agree. We don't wanna make Scratch “too easy”.

DualPikachu wrote:

ThatExplosivePigeon wrote:

ham07 wrote:

i agree, adding some of them would be great yet some ,such as all at once, is best staying out of scratch.

All at once has some uses, in snap and other ones, but run without screen refresh, has completely destroyed it. I agree with you, lets not add that one back.

I agree. We don't wanna make Scratch “too easy”.

Then we would fall into the trap of microsoft makecode, where every block is so specific, its hardly a hard programming lanugage anymore.

ThatExplosivePigeon wrote:

DualPikachu wrote:

ThatExplosivePigeon wrote:

ham07 wrote:

i agree, adding some of them would be great yet some ,such as all at once, is best staying out of scratch.

All at once has some uses, in snap and other ones, but run without screen refresh, has completely destroyed it. I agree with you, lets not add that one back.

I agree. We don't wanna make Scratch “too easy”.

Then we would fall into the trap of microsoft makecode, where every block is so specific, its hardly a hard programming lanugage anymore.

I'm not saying I wanna make Scratch too hard or too easy, Scratch is supposed to be a introduction programming language.

DualPikachu wrote:

ThatExplosivePigeon wrote:

DualPikachu wrote:

ThatExplosivePigeon wrote:

ham07 wrote:

i agree, adding some of them would be great yet some ,such as all at once, is best staying out of scratch.

All at once has some uses, in snap and other ones, but run without screen refresh, has completely destroyed it. I agree with you, lets not add that one back.

I agree. We don't wanna make Scratch “too easy”.

Then we would fall into the trap of microsoft makecode, where every block is so specific, its hardly a hard programming lanugage anymore.

I'm not saying I wanna make Scratch too hard or too easy, Scratch is supposed to be a introduction programming language.

I guess, scratch has to have just a low enough floor, and a just about high enough ceiling for it to fufill its purpose

There are some arguments about which blocks should be added and which should not. Cooldown time, I'll ask for this to be reopened. Closing in 24 hrs, or reply now.

dhfbei8987 wrote:

There are some arguments about which blocks should be added and which should not. Cooldown time, I'll ask for this to be reopened. Closing in 24 hrs, or reply now.

I don’t think the Scratch Team intends topic closing to work that way.

There's also these other hidden blocks too:



Do you want these back too? I can't think of a use for them.