fdreerf wrote:

This might be a little tricky to do on the online editor as the Scratch logo is a link.

I'm not sure about that. The Scratch logo is fixated at the very top left of screen, so theoretically it should be extremely easy to put something over it with “position: absolute”. Or you could use onmousedown to handle the link and check for clientX and clientY.

Edit: Ayy, king of the page!

There also is a

al at once {
} :: control

but it doesn't do anything anymore.

SaltyTree wrote:

There also is a

al at once {
} :: control

but it doesn't do anything anymore.

I know, that's why I specified “functional” hidden blocks. There are a bunch more hidden blocks which only exist for legacy compatibility than just that one.

the2000 wrote:

I'm not sure about that. The Scratch logo is fixated at the very top left of screen, so theoretically it should be extremely easy to put something over it with “position: absolute”. Or you could use onmousedown to handle the link and check for clientX and clientY.

Edit: Ayy, king of the page!

The best thing to do would be probably to put another link over it with position: absolute and the same href. When clicked, it would check if shift is pressed, if so, it would call event.preventDefault and toggle the hidden blocks, otherwise it would go to the Scratch homepage like normally. Same for the offline editor: if you hold shift while clicking it would toggle the blocks, otherwise it would open the about window.

Maximouse wrote:

the2000 wrote:

I'm not sure about that. The Scratch logo is fixated at the very top left of screen, so theoretically it should be extremely easy to put something over it with “position: absolute”. Or you could use onmousedown to handle the link and check for clientX and clientY.

Edit: Ayy, king of the page!

The best thing to do would be probably to put another link over it with position: absolute and the same href. When clicked, it would check if shift is pressed, if so, it would call event.preventDefault and toggle the hidden blocks, otherwise it would go to the Scratch homepage like normally. Same for the offline editor: if you hold shift while clicking it would toggle the blocks, otherwise it would open the about window.

brb making a bookmarklet that checks for this now

yeah this would be a good feature though they probably wont add it (it doesn't seem like they add suggestions much anymore)

Support, I don't see why not.

Maximouse wrote:

the2000 wrote:

I'm not sure about that. The Scratch logo is fixated at the very top left of screen, so theoretically it should be extremely easy to put something over it with “position: absolute”. Or you could use onmousedown to handle the link and check for clientX and clientY.

Edit: Ayy, king of the page!

The best thing to do would be probably to put another link over it with position: absolute and the same href. When clicked, it would check if shift is pressed, if so, it would call event.preventDefault and toggle the hidden blocks, otherwise it would go to the Scratch homepage like normally. Same for the offline editor: if you hold shift while clicking it would toggle the blocks, otherwise it would open the about window.

If toggle of showing these hidden blocks would be made by something like you said, I support!

There is also bunch more like the sound_sounds_menu:

([costume1 v] :: looks)
([mouse-pointer v] :: sensing)
([mouse-pointer v] :: motion)
([myself v] :: control)

see this project: https://scratch-mit-edu.ezproxyberklee.flo.org/projects/382631312/editor/ in the Dropdowns sprite for more.

How have I not seen this suggestion? Support! I'd love to be able to easily access hidden cool blocks! That way, it won't confuse newcomers, but oldcomers can easily use advanced blocks to make their projects more efficient.

Honestly I just want back the ability to create custom hacked blocks because that was the coolest thing ever.

However, this is a good suggestion, it's just that there are so few hacked blocks that they would just be better off in the main block pallette,

Ihatr wrote:

there are so few hacked blocks that they would just be better off in the main block pallette

Well, I think the ST feels otherwise about that.

Bump. I assume there would be something on the wiki about this so people other than us forumers can enjoy them.

Ihatr wrote:

However, this is a good suggestion, it's just that there are so few hacked blocks that they would just be better off in the main block pallette,

Yeah. Plus, having features tucked away in some obscure place where most don't have access to them doesn't seem like the right move to me. Every block should be equally accessible to everyone.

Nice idea, but I would just like these in the block editor. For each variable in 10 is a useful block. Maybe there could be a extension which is ‘other blocks’ and it gets those blocks out!

the2000 wrote:

 <loud? :: sensing> 

The loud? block about to be existed in scratch 0.6 to scratch 2.0, I remember i used the loud? block on scratch 1.4 offline editor.

Anyway ill support it.

Is this unconstructive post?

boncuk18 wrote:

scratch 0.6 to scratch 2.0

Scratch 0.6 to Scratch 1.4

I support! 100% because of the for loop block.

sathvikrias wrote:

boncuk18 wrote:

scratch 0.6 to scratch 2.0

Scratch 0.6 to Scratch 1.4

no it even existed pre-alpha, alpha and beta (with other 2.0 development versions)

boncuk18 wrote:

sathvikrias wrote:

boncuk18 wrote:

scratch 0.6 to scratch 2.0

Scratch 0.6 to Scratch 1.4

no it even existed pre-alpha, alpha and beta (with other 2.0 development versions)

yeah, the scratch wiki isn't really specific with the alpha and beta stuff unless that is the only time when the block existed.