A VERY simple thing that could prove useful, because other forms of it has.

The_Scratch_Squad

thelucariokid wrote:
I think there should be a block
 show monitor [ v]::sensing
And it would do the same thing as all those blocks combined.

What… does that show?

As for the topic, support!

REMEMBER! Clicky That Sticky AND Read it Carefully before making new topics.
Get the Worlds Fails on Math!!!

Nether_before

Support!

~~If life gives you kumquats, lock your signature up, bury it in the ground and hope it's safe~~
hello child. i am an elf

DaSpudLord

Scratchifier wrote:
No support…
set [timer v] to (timer)
show variable [timer v]
etc

No support due to this.

| Primary Target | Fireworks Show! Wheel of Fortune || Block Buster ||||| Shut the Box ||||||||| Surf's Up! |||||

U^ｪ^U::motion//This is Blocky. He lives in my signature. He is a trained attack block. He protects my siggy from kumquats.

Cosmicstars-

Scratchifier wrote:
No support…
set [timer v] to (timer)
show variable [timer v]
etc

^^
Workaround, so no support.

Cosmicstars-
My suggestion: None
My projects: …
100 posts ??/??/????
200 posts ??/??/????
300 posts Soon.
Let's bring back

(user id ::sensing)

Support us!

TheMonsterOfTheDeep

I don't like that workaround because it requires an extra forever loop that could be avoided with this block. Also, the workaround doesn't update when the value itself does, so you have a watcher showing inaccurate values. That's no fun.

I support the block suggested above:

show watcher [x position v] :: sensing

It has a list of all the non-variable watchers.

my latest extension: 2d vector math

BoyKetchup

bobbybee wrote:
I don't like adding so many repetive blocks. Perhaps just a:
show watcher [timer v] :: sensing
block (in data, perhaps)

I agree, this is much better.

Meese123

thelucariokid wrote:
I think there should be a block
 show monitor [ v]::sensing
And it would do the same thing as all those blocks combined.

^^^^^

If you see this block while scrolling

when Meese123 {say (username::grey) in {[Portuguese v]::hat control}::operators} clicked {<Meese123=awesome::sound>true::cap motion}::hat looks

you have been visited by Sir Programmer VI
the ability to program almost as well as him will come to you
but only if you comment "Moo. I am a banjo playing rhinoceros" on my profile.
Family: @Meese123 @Moo89 @PandaBearK @bixitrixy Alt account: @pitbelly | Go here please!!

_Hope

thelucariokid wrote:
I think there should be a block
 show monitor [ v]::sensing
And it would do the same thing as all those blocks combined.

I think the separation of each item into their own category of blocks is important.

5955595595 5599995559995999555595559999955599959559595
5955595595 5955555595555955955959555595555955559559595
5999995595 5599955955555999559555955595559555559999595
5955595595 5555595595555959559999955595555955559559555
5955595595 5999955559995955959555955595555599959559595
Highlight the numbers, press Ctrl + F, press 9, and press Enter/Return. Or for Mac, CMD + F.

seanbobe

when green flag clicked
forever
    
set [timer v] to (timer)
end

define show timer
show variable [timer v]

Sadly my kumquat was eaten by an evil signature.
_______________
|My internets.…..|
\Kumquat Shield/

BlueCrayfish

Hate that workaround. 100000000000*support

Does this pique your interest:
A 26 year old accountant was framed for changing records, who, now a fugitive, flees, and tries to find the organization who actually coordinated the scam.

Would you be interested in joining:
A collab that is checked every day and managed well.

Then why don't you click the sunglasses guy?

rollercoasterfan

Scratchifier wrote:
No support…
set [timer v] to (timer)
show variable [timer v]
etc

when [chromometer altimeter v] = [5th length v] and [7th length v] with a [gap v] of (17) ::events hat
forge [chromometer v] altimeter until < (speed) = (velocity)> ::control cstart
	switch places with (759 v) altimeters with value of (speed) ::looks
	control [altimeter 1 v] at time (10):(17):(58) ::control
end
initialize sequence (24) so [object 3 v] moves to x (156) y (231) ::control
reveal [final answer v] and stop running this script ::events cap

WSStudent2

_Hope wrote:
What I am suggesting:
show timer :: sensing
hide timer :: sensing

show x position :: motion
show y position :: motion
show direction :: motion

show mouse x :: sensing
show mouse y :: sensing

show volume :: sound
Other forms that has been VERY useful to people using Scratch:
show variable [ v]
hide variable [ v]

show list [ v]
hide list [ v]
I know it's not that much, but it's enough. I mean, showing and hiding variables: what would Scratch be like without it?
er..
7 supporters, 7 non-supporters…

I support! This is a great idea!!

Pot-of-Gold

_Hope wrote:
What I am suggesting:
show timer :: sensing // use variables
hide timer :: sensing

show x position :: motion // variables
show y position :: motion // variables
show direction :: motion // variables

show mouse x :: sensing // ^^
show mouse y :: sensing // ^^

show volume :: sound
Other forms that has been VERY useful to people using Scratch:
show variable [ v]
hide variable [ v]

show list [ v]
hide list [ v]
I know it's not that much, but it's enough. I mean, showing and hiding variables: what would Scratch be like without it?
er..
7 supporters, 7 non-supporters…

Also, the only one that is really nessescary is the timer.

Click to play

Zro716

I support. I mean, sure there's the workaround, but I'm one of those programmers who has a need for spatial restraint, so I loathe having to double the number of variables just to do this sort of thing. Another thing to take note is that most of those built-in variables have their own set and change blocks, and it would make sense to complement the user variable show/hide blocks, like this:

show motion variable [x position v] ::motion
show looks variable [costume v] ::looks
show sound variable [tempo v] ::sound
show sensing variable [timer v] ::sensing
// similar for hide blocks....

Last edited by Zro716 (June 25, 2015 07:53:54)

As a long time Scratcher, I have found new meaning to the name “Scratch”: for me, it means to “scratch that itch”, to come back again and again to realize new ideas in this toy language, even when I'm capable of creating my projects in real programming languages years later. It's a friend that helped me to pursue programming and get me to enjoy its fruit. I'm certain many others who have walked this path as well have grown fond of its importance in their life.

matey1234

JamesOuO wrote:
Scratchifier wrote:
No support…
set [timer v] to (timer)
show variable [timer v]
etc
Ah, didn't think about this workaround.
Very easy workaround, no support.

– – – matey1234 – – –

seanbobe

[show v] [timer v] :: sensing

Sadly my kumquat was eaten by an evil signature.
_______________
|My internets.…..|
\Kumquat Shield/

_Hope

Zro716 wrote:
I support. I mean, sure there's the workaround, but I'm one of those programmers who has a need for spatial restraint, so I loathe having to double the number of variables just to do this sort of thing. Another thing to take note is that most of those built-in variables have their own set and change blocks, and it would make sense to complement the user variable show/hide blocks, like this:
show motion variable [x position v] ::motion
show looks variable [costume v] ::looks
show sound variable [tempo v] ::sound
show sensing variable [timer v] ::sensing
// similar for hide blocks....

I see.

5955595595 5599995559995999555595559999955599959559595
5955595595 5955555595555955955959555595555955559559595
5999995595 5599955955555999559555955595559555559999595
5955595595 5555595595555959559999955595555955559559555
5955595595 5999955559995955959555955595555599959559595
Highlight the numbers, press Ctrl + F, press 9, and press Enter/Return. Or for Mac, CMD + F.

-FlameUprising-

thelucariokid wrote:
I think there should be a block
 show monitor [ v]::sensing
And it would do the same thing as all those blocks combined.

^^^^^^^ Yes.

Pie Simulator 2015

Pot-of-Gold

List the reasons you need all those. The only one that is really nesscesary is timer. All the others. Not important

Click to play

Discuss Scratch