Hide and Show reporter variables

Giranems101

Idea:
Two new blocks in the Sensing category that let scripts show or hide specific built-in reporters on the stage at runtime.

hide reporter [x position v]::sensing

show reporter [y position v]::sensing

Right now, reporter monitors visibility can only be toggled manually in the blocks palette. This means you can’t turn them on or off during a project runtime. These blocks would allow cleaner projects by hiding monitors automatically.

Allowed reporters:
Only the built-in reporters that can already appear on the stage:

x position
y position
direction
costume [name v]
costume [number v]
backdrop [name v]
backdrop [number v]
size
volume
answer
loudness
timer
current [year v]
current [month v]
current [date v]
current [day of week v]
current [hour v]
current [minute v]
current [second v]
username

(Excluding things like mouse x, mouse y, and days since 2000, since those can’t be shown as monitors.)

Why this is a good idea
Scratch already supports showing/hiding variable and list monitors in the runtime while reporters cannot. This would simply make that possible, making the default reporter monitors further useful, without having to create a variable for the same.

francottt

good idea! also, somewhere in a project called “hacked blocks” someone has accomplished this, so I suggest you go take a look for a temporary solution!

Giranems101

francottt wrote:
good idea! also, somewhere in a project called “hacked blocks” someone has accomplished this, so I suggest you go take a look for a temporary solution!

Can you send me the link cuz there's like a million projects named “hacked blocks”?

Giranems101

francottt wrote:
good idea! also, somewhere in a project called “hacked blocks” someone has accomplished this, so I suggest you go take a look for a temporary solution!

also this might seem a bit silly but can you tell me how you manipulated the code in your signature to have an OPERATORS CAP BLOCK?

CoolLock

I'm 99% sure this is a duplicate but I can't find the original somehow.

cubetube7

Giranems101 wrote:
francottt wrote:
good idea! also, somewhere in a project called “hacked blocks” someone has accomplished this, so I suggest you go take a look for a temporary solution!
also this might seem a bit silly but can you tell me how you manipulated the code in your signature to have an OPERATORS CAP BLOCK?

https://www.en.scratch-wiki.info/wiki/Block_Plugin/Syntax

dizzyboy42

maybe instead it should be

[hide v] reporter (variable v)::sensing

so they can put reporters in there

FreshTheCat

dizzyboy42 wrote:
maybe instead it should be
[hide v] reporter (variable v)::sensing
so they can put reporters in there

Or

show variable (variable v) ::variables
show variable (foo) ::variables
show variable (x position ::motion reporter) ::variables

show variable (variable v) ::variables
show variable (foo) ::variables
show variable (x position ::motion reporter) ::variables

jmdzti_0-0

this behavior currently is only possible through json editing

FreshTheCat

Giranems101 wrote:
francottt wrote:
good idea! also, somewhere in a project called “hacked blocks” someone has accomplished this, so I suggest you go take a look for a temporary solution!
also this might seem a bit silly but can you tell me how you manipulated the code in your signature to have an OPERATORS CAP BLOCK?

whatever (reporter ::sensing reporter) number(9) [string] or (variable) you want in an operators cap :: operators cap

whatever (reporter ::sensing reporter) number(9) [string] or (variable) you want in an operators cap :: operators cap

Also, here's a

lists hat with an (events boolean ::events boolean) ::list hat

lists hat with an (events boolean ::events boolean) ::list hat

Sorry for potential blockspam

Discuss Scratch