Discuss Scratch
- Discussion Forums
- » Advanced Topics
- » Scratch 3.0 Technical Discussion
- MinecraftM153
-
100+ posts
Scratch 3.0 Technical Discussion
I think you should add an Else - If block.
No, you can already replicate it using normal means
- Greenduck54
-
500+ posts
Scratch 3.0 Technical Discussion
Yes, it's workaroundable, but which is clearer to read?I think you should add an Else - If block.
No, you can already replicate it using normal means
This:
if <...> thenOr This:
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
if <...> then
...
else
...
end
end
end
end
end
end
end
end
end
end
end
end
//same script as aboveI'd prefer the second one for long scripts like that. This is why people suggest else if. Not because they need it for something, but so they can more easily read their code.
if <...> then //couldn't make else if go into the block itself :P
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else if <...> then ::control
...
else
...
end
Last edited by Greenduck54 (April 27, 2018 17:16:54)
- 77Tigers
-
62 posts
Scratch 3.0 Technical Discussion
Here's a more readable workaround: I'd prefer the second one for long scripts like that. This is why people suggest else if. Not because they need it for something, but so they can more easily read their code.
define workaround (input)(Also:
if <(input)... ::operators> then
...
stop [this script v]
end
if <(input)... ::operators> then
...
stop [this script v]
end
if <> then {)
} else if <> {
} else {
}::control
Last edited by 77Tigers (April 27, 2018 18:13:43)
- _nix
-
1000+ posts
Scratch 3.0 Technical Discussion
That's a good workaround, except for when you want to put a “stop this script” into the elseif itself – then you have to do something like this: Here's a more readable workaround:define workaround (input)
if <(input)... ::operators> then
...
stop [this script v]
end
if <(input)... ::operators> then
...
stop [this script v]
end
define my block
say [hello!!!!]
workaround
if <(stop this script) = [yes]> then
stop [this script v]
end
say [whee]
define workaround
set [stop this script v] to [no]
if <some condition :: grey> then
...
stop [this script v]
end
if <some condition :: grey> then
set [stop this script v] to [yes]
stop [this script v]
end
if <some condition :: grey> then
...
stop [this script v]
end
But this discussion is really better fit for a discussion thread specifically dedicated to else-if.
- NitroCipher
-
500+ posts
Scratch 3.0 Technical Discussion
Just a reminder, this thread is meant to be focused on information, discussion, and questions.
This is not a place for suggestions, for that go here
This is not a place for suggestions, for that go here
- ACE009
-
100+ posts
Scratch 3.0 Technical Discussion
I saw this too. The main problem is that variable check-boxes are completely hidden. I found a bug. When you have several extensions loaded, or you are maybe using a small screen, the scroll bar of the category list goes above the blocks in the palette.
- ACE009
-
100+ posts
Scratch 3.0 Technical Discussion
Another problem: broadcast and variable drop down menus don't have a data-argument-type tag like the rest of the inputs do, messing up CSS styles for the editor.
- LEGAMER4665
-
84 posts
Scratch 3.0 Technical Discussion
In the 3.0 version (not just the gui), It will be the
for each [ v] in (10) :: variablesblock?
- _nix
-
1000+ posts
Scratch 3.0 Technical Discussion
That hacked block will be supported, so projects that use it will still work, but it won't be in the block palette (i.e. the list of blocks). In the 3.0 version (not just the gui), It will be thefor each [ v] in (10) :: variablesblock?
- MrMeowington
-
100+ posts
Scratch 3.0 Technical Discussion
I don't know; this partThe new style is going to extend to every page. -snip-
I'm not sure there will be many other tweaks. As far as I know the homepage will be staying the same.

seems pretty 2.0ish and should probably be changed. Also, the entirety of the discussion forums just SCREAMS 2013.
Last edited by MrMeowington (April 28, 2018 03:17:58)
- Sheep_maker
-
1000+ posts
Scratch 3.0 Technical Discussion
this partWhy should it be changed? There's nothing wrong with it. Just because the website underwent a rewrite between 1.4 and 2.0 doesn't mean it has to happen for every major update of the Scratch editor. I don't know;
seems pretty 2.0ish and should probably be changed.
They haven't started the redesign of the discussion forums yet Also, the entirety of the discussion forums just SCREAMS 2013.assuming they decide to keep it
- MrMeowington
-
100+ posts
Scratch 3.0 Technical Discussion
-snip-
List monitors are scheduled for implementation in March / April.
Ummm… April is almost over, and we still don't have list monitors…
(I checked here, and you should too so you can see them as soon as they add them.)
- MrMeowington
-
100+ posts
Scratch 3.0 Technical Discussion
True, I just think that Helvectia Bold wouldn't look the best in that context for 3.0.this partWhy should it be changed? There's nothing wrong with it. Just because the website underwent a rewrite between 1.4 and 2.0 doesn't mean it has to happen for every major update of the Scratch editor. I don't know;
seems pretty 2.0ish and should probably be changed.
Did you mean "assuming they decide to change it?"They haven't started the redesign of the discussion forums yet Also, the entirety of the discussion forums just SCREAMS 2013.assuming they decide to keep it
- NickyNouse
-
1000+ posts
Scratch 3.0 Technical Discussion
It looks like they rescheduled it for May, but yeah I'm not seeing any development on it yetUmmm… April is almost over, and we still don't have list monitors… -snip-
List monitors are scheduled for implementation in March / April.
(I checked here, and you should too so you can see them as soon as they add them.)
They did recently remove Discuss from the toolbar, it's not too crazy to imagine that they might be phasing the forums out (don't freak out though, I don't think the ST has said anything like that). Honestly to me it looks like they're just downplaying the forums but are totally gonna leave them up. They're still using them for announcements and stuff, after all.Did you mean "assuming they decide to change it?"They haven't started the redesign of the discussion forums yet Also, the entirety of the discussion forums just SCREAMS 2013.assuming they decide to keep it
- follingeneric17
-
41 posts
Scratch 3.0 Technical Discussion
Seems like that with the bitmap editor, they add the next feature every so often. You can only use the line and paintbrush tools right now.
- ACE009
-
100+ posts
Scratch 3.0 Technical Discussion
Although neither control or shift make the lines adhere to 45 or 90 degree increments. (45 is better) Seems like that with the bitmap editor, they add the next feature every so often. You can only use the line and paintbrush tools right now.
- PumpkinBear111
-
68 posts
Scratch 3.0 Technical Discussion
What is Scratch 3.0 going to be made in? Is it still going to need flash even though flash will be dead by 2020?
- PumpkinBear111
-
68 posts
Scratch 3.0 Technical Discussion
Is there going to be a Scratch 2.0 to Scratch 3.0 converter?