Put reporters + booleans in dropdowns...

Scratcher1002

Self-explanitory, this would eliminate the need for certain “hacked” blocks.

CatsUnited

Support, not sure why someone wouldn't want it without JSON editing.

Scratcher1002

CatsUnited wrote:
Support, not sure why someone wouldn't want it without JSON editing.

For this:

((amazing variable... thingy) of [Sprite1 v])

CatsUnited

Scratcher1002 wrote:
CatsUnited wrote:
Support, not sure why someone wouldn't want it without JSON editing.
For this:
((amazing variable... thingy) of [Sprite1 v])

Or

<key (var) pressed?>

, which could be used to detect shift, ctrl, enter, etc.

ChildCritic

Workaroundable using JSON hacking, but that's not vanilla scratch and I don't know how to do it.
Support.

Prinseskat

Support - I don't think the ST really likes hacked blocks (there was a post on the forums about it somewhere, can't find it now), so this would be in both our favour as JSON hacking is annoying, and their favour as it wouldn't happen as much.

DaSpudLord

Zekrom01 wrote:
ChildCritic wrote:
Workaroundable using JSON hacking, but that's not vanilla scratch and I don't know how to do it.
Support.

Prinseskat wrote:
Support - I don't think the ST really likes hacked blocks (there was a post on the forums about it somewhere, can't find it now), so this would be in both our favour as JSON hacking is annoying, and their favour as it wouldn't happen as much.

Scratcher1002

Zekrom01 wrote:
ChildCritic wrote:
Workaroundable using JSON hacking, but that's not vanilla scratch and I don't know how to do it.
Support.

This is a win for them, (no more hacking the key pressed block). And win for us for the same reason.

Plus this:

Key (join [shift] []) pressed? :: sensing boolean

gamebeater187

Like

if [1 = 0 v] :: events cstart

?

Last edited by gamebeater187 (Nov. 1, 2015 01:34:48)

Scratcher1002

gamebeater187 wrote:
Like
if [1 = 0 v] :: events cstart
?

No, like:

Key [space v] pressed? :: sensing boolean // That drop down isn't usable with variables normally, so why not:
Key (join [space] []) pressed? :: sensing boolean

gamebeater187

Scratcher1002 wrote:

gamebeater187 wrote:
Like
if [1 = 0 v] :: events cstart
?

No, like:

Key [space v] pressed? :: sensing boolean // That drop down isn't usable with variables normally, so why not:
Key (join [space] []) pressed? :: sensing boolean

Support.

Scratcher1002

Blue
Unicorns
Make
Penguins

Zekrom01

Scratcher1002 wrote:
Blue
Unicorns
Make
Penguins

they do

Scratcher1002

Zekrom01 wrote:
Scratcher1002 wrote:
Blue
Unicorns
Make
Penguins
they do

Xd

Nether_before

Support. I could see this being useful, but how would one like this work?

Key (join [space] []) pressed? :: sensing boolean

How would the editor know that “space” is referring to the space key on the keyboard?

Last edited by Nether_before (Nov. 8, 2015 19:49:33)

DaSpudLord

Nether_before wrote:
Support. I could see this being useful, but how would one like this work?
Key (join [space] []) pressed? :: sensing boolean 
How would the editor know that “space” is referring to the space key on the keyboard?

<key [space v] pressed?>

Space is already an option in the dropdown. So I think it would work. It would just coordinate to the “space” item in the dropdown menu. This is comparable to costumes-

switch to costume (join [costume][1])

Scratch knows this is referring to the item in the dropdown titled “costume1,” so it works. And if there is no item titled “costume1,” then it doesn't do anything. In the case of the key pressed block, if someone entered in a nonexistant/nonsupported key, it would always report false.

Last edited by DaSpudLord (Nov. 8, 2015 20:52:52)

Scratcher1002

DaSpudLord wrote:
Nether_before wrote:
Support. I could see this being useful, but how would one like this work?
Key (join [space] []) pressed? :: sensing boolean 
How would the editor know that “space” is referring to the space key on the keyboard?
<key [space v] pressed?>
Space is already an option in the dropdown. So I think it would work. It would just coordinate to the “space” item in the dropdown menu. This is comparable to costumes-
switch to costume (join [costume][1])
Scratch knows this is referring to the item in the dropdown titled “costume1,” so it works. And if there is no item titled “costume1,” then it doesn't do anything. In the case of the key pressed block, if someone entered in a nonexistant/nonsupported key, it would always report false.

Though we can already do the costume thing.

I could see it being used for:

((something) of [Sprite1 v])

Scratcher1002

Balloons Use Many Propulsions

Last edited by Scratcher1002 (Feb. 10, 2016 22:22:51)

Scratcher1002

Superbump.

sundun

ChildCritic wrote:
Workaroundable using JSON hacking, but that's not vanilla scratch and I don't know how to do it.
Support.

^^^^

Discuss Scratch