Special Comment Blocks

CosmicHamster

theonlygusti wrote:

Wow…
What an idea.

Total support!

And it could also blend with the color of whatever block it is on.

Support for this ^^

MegaApuTurkUltra

Support!

Cosmicstars-

I support!

Prinseskat

Support! C-block comments could even be combined with this idea to make things even better.

bendylover48

AonymousGuy wrote:

They were removed because of confusion.

And, there is an easy workaround, so no support:

define REM (comment)

when gf clicked
REM [This is run when the program starts.]
go to x: (0) y: (0)
REM [This resets the sprite's position.]
if <not <[This is a C block comment. They aren't found in any other programming languages in existence.] = []>> then
forever
if <not <[This checks to see if the user is pressing space.] = []>> then
if <key [space v] pressed?> then
say [Hello!]
REM [This will say "Hello!" when the space key is pressed.]
else
say []
REM [This will say nothing when space isn't pressed.]
end
end
end
end
[quote=AonymousGuy]They were removed because of confusion.

And, there is an easy workaround, so no support:
[scratchblocks]
define REM (comment)

when gf clicked
REM [This is run when the program starts.]
go to x: (0) y: (0)
REM [This resets the sprite's position.]
if <not <[This is a C block comment. They aren't found in any other programming languages in existence.] = []>> then
forever
if <not <[This checks to see if the user is pressing space.] = []>> then
if <key [space v] pressed?> then
say [Hello!]
 [This will say "Hello!" when the space key is pressed.]
else
say []
REM [This will say nothing when space isn't pressed.]
end
end
end
end
[/scratchblocks][/quote]

-Snipet-

This is a really good idea!

Paddle2See

https://scratch.mit.edu/discuss/post/4903222/

the2000

Paddle2See wrote:
https://scratch.mit.edu/discuss/post/4903222/

I think this seems like a different idea entirely, and one which I could personally sorta get behind. If it is indicated well visually (i.e. all of the blocks in the loop become grey) then I don't think that being confusing should be an issue at all.

marshmallowop

Support :: control

I am learning and I find that this suggestion is not just useful, but an important feature, there seems to be no practical work around to it that does not involve some sort of inconvenient and potential confusion as for how the work around uses blocks in an unorthodox way.

As Scratch is a learning programming language, it is important to teach about the importance of commenting your scripts.
And much more when Scratch team is so vivid and energetic about remixing and allowing others to learn and see other´s work in detail, where commenting block would play a very important programming lesson (sharing information to handle and manage other´s scripts).

Nowadays I almost see no comment textbox or that “work arounds” people have spoke about in this topic (I actually have just seen one project commenting their scripts), and it is likely because the lack of this block, Scratch lacking commentary feature is quite concerning.

SuperMarioHome

what does ukraine have to do with this

soarroying

Easy workaround:

//Right click anywhere on the code editor and select "add comment" or
define comment [comment]
//Put no blocks in define

comment [I'm a comment from the Scratch 3.0 beta! v]

No Support, we don't need this block, it's already obsolete, for reasons, not under my control.

superbuddy2

TimothyLawyer wrote:
(#8)
Here is a way to comment inline:
think (letter (0) of [comment here])
Or if already using ‘think’ or ‘say’ then wrap like so.
if <>
think [comment here]
end
And for C block:
if <> then
    think [comment here]
else
... code ... ::grey
end
Or use a custom block with no definition.
note [ ] ::custom

if <>
   note [comment here]
else
   ... code ... ::grey
end

define note [ ]
Or
define comment []
The color and the font in the Handle Physics definitions look really nice. Wish we had a way to replicate.

The C-Block could be replicated with this:

if <(0)=((Comment) * (0))> then
code here... :: grey
end

As for the stack block, to avoid messing up stuff with say block, etc. just use this:

comment ()

define comment (comment)

randomguy3513

the2000 wrote:
Paddle2See wrote:
https://scratch.mit.edu/discuss/post/4903222/
I think this seems like a different idea entirely, and one which I could personally sorta get behind. If it is indicated well visually (i.e. all of the blocks in the loop become grey) then I don't think that being confusing should be an issue at all.

I would consider it still rejected, all blocks should at least do something and comments don't do anything so I'd still consider it rejected and C-comment-blocks don't loop like other C-blocks.
(also, I don't know what the second comment block is so I am not gonna talk about that one)

Discuss Scratch