WindOctahedron wrote:

So we can consider “bring back user id” rejected. Am I right?

Za-Chary wrote:

WindOctahedron wrote:

So we can consider “bring back user id” rejected. Am I right?

After looking into what that block is, I'd say we wouldn't be bringing it back just because we made the decision to remove it before Scratch 2.0 was officially released. The “username” block does pretty much the exact same thing. Although I can't say for sure if it really is rejected.

Has anyone suggested bringing the “user id” block back? I'm not really sure what it could do that the “username” block can't do.

Za-Chary wrote:

WindOctahedron wrote:

So we can consider “bring back user id” rejected. Am I right?

Has anyone suggested bringing the “user id” block back?

I'm not really sure what it could do that the “username” block can't do.

Scratch Wiki article about "user id" wrote:

Each user had a different ID according to when they viewed the project (the first viewer was 1, the second was 2, and so forth). Users who were not logged in to an account were assigned the user ID 0. User ID's remained constant for the same project. The user ID block itself was a reporter block, and belonged to the Sensing category.

AAmania wrote:

I've been wondering, what did the “user id” block do compared to the “username” block?

when green flag clicked
if <key [Rejecto!!! v] pressed?> then 

  
say [why did they come up with these if they are rejected??] for (2) secs

else
say [press rejecto]
end

2005200439 wrote:

Hello, nice topic !

WindOctahedron wrote:

Dragonlord767 wrote:

Am I just missing something, or has “Exact post counts” been removed from this list?

It's item 9.2.

• Explain why an account is being banned for being an alternate account
  
  
• Option or warning for typing “colour” on the forums
  
  
• Let everyone get featured
  
  
• Rename “Questions about Scratch” to “Questions”
  
  
• Nested lists
  

Paddle2See* wrote:

I consider those all rejected. Confusing to beginners - not that hard to implement for experienced programmers.

1.7 2D lists
2D lists, also known as 2D arrays, nested lists, or matrices, are a type of data structure that allows you to put an entire list as an element of another list; that is, it allows you to put lists inside of lists. These sorts of data structures are used widely in other programming languages.

The block below, and others, would allow you to create 2D lists to store information, sort of like a table. However, this is too complicated for what is supposed to be an introductory programming language. In addition, there are workarounds possible by using an ordinary list and an indexing function.

For those who are interested, it may be worth checking out Snap. It is a block-based programming language designed for more experienced programmers, and has more advanced data structures than Scratch does.

add () to sublist () of [list v] :: list

Za-Chary wrote:

Yep, Paddle responded to my query. When I asked if “nested lists” are the same as “2D arrays” or “matrices”, he responded with this:

Paddle2See* wrote:

I consider those all rejected. Confusing to beginners - not that hard to implement for experienced programmers.

This has been suggested a number of times, and so I will be adding it to the list eventually.

Za-Chary wrote:

This has been suggested a number of times, and so I have added it to the list, under 1.7.

-snip-

WindOctahedron wrote:

-snip-

wojciech-marzec wrote:

go to x: () y: () z: () :: motion

The z-axis in Scratch could refer to ‘layer’, not how close to the screen the object is.

cawdd wrote:

wojciech-marzec wrote:

go to x: () y: () z: () :: motion

The z-axis in Scratch could refer to ‘layer’, not how close to the screen the object is.

rosebud87 wrote:

If you all want text-based coding, tynker.com is a lot like Scratch 1.4 in the layout, but it has some other blocks, as well as text-based coding and Minecraft mods.

DaEpikDude wrote:

“Mouse up?” block has been rejected (probably not worth putting it on the list but it's there)

AKpanda7 wrote:

Could you make a block so that we could view who viewed are project or were you can love and favorite maybe if you click on the eye button it can show you a list of scratchers who viewed your project?

Za-Chary wrote:

Asking someone to participate in follow for follow is relatively harmless. It is also not enforceable; how do you stop someone from doing follow for follow? If someone asks you to do follow for follow, and you do not want to, just politely decline their request. If they keep spamming you with requests, you can report that user.