ItsMushroomYt1104 wrote:

Okeyeyeyeyeyeyey

Remove the lag: You put wait blocks in every repeat/forever loop, which causes everything to move slowly. If you didn’t know, Scratch runs at 30fps, so removing those wait blocks will not cause your code to run instantly (that only applies to custom blocks that run without screen refresh). What this could do:
The introduction animation can be more smooth
Pen strokes will be less straight and slow
Scratch is weird with wait blocks, so wait 0.1 seconds doesn’t wait 0.1 seconds. If you want the eraser timer to be accurate, put in a repeat 2 that runs move 0 steps in the eraser timer loop.
More colours: 21 colours is a lot… a lot more than TechnoShyft’s, but why not give users… say… over 16 million colours? How you can achieve this:
In the more colours tab, you could make variables red, green and blue be shown. These are sliders that have a range from 0 to 255 (no decimals). You can then set the pen colour to it, by doing this: Note: it’s the colour with the colour selection, not the pen colour with a number. You can then make the colour buttons instead change the red green and blue values. They don’t have to be exact, but if you want to find the exact RGB values, you can use an external tool for it.
Colour display: Instead of giving every colour a name, you can have a dynamic colour display by having a sprite that has a large pen size always have its pen down and set its pen colour to those RGB values said before.
Cleaner code: Instead of putting a whole bunch of Boolean blocks in a single if block, you can replace it with a much cleaner and easier to edit method: In the backdrop, put a when stage clicked block and make it broadcast a message (say “draw”). When the pen sprite receives that message, set the pen colour to whatever colour you have selected, pen down, wait until not mouse down and pen up. Why have it set the pen colour in that script? Well…
Erase mode: Instead of using a timer and stamping a white circle, you can make it toggle erase mode. It’ll set the erase mode variable to 1 when on and 0 when off. In the pen sprite, the reason why the pen colour gets set in that script is so that you can put an if else around it. If erase mode = 0, it’ll set the colour to whatever you chose. Else, it’ll set the pen colour to white. This also prevents dots from appearing or holes when moving too fast, and lets the user change eraser size. (If you instead want a lazier option, you can just add the colour white)
Easier size selection: Replace the + and - buttons with a size button. When clicked, it’ll show a slider to set the pen size with a range from 1 to 100. Additionally, you can make it so that you can double tap the size button to type. How to do it: Make a variable called “slider” for the size button sprite only. It will be set to 0 at the start of the project. When this sprite is clicked, if slider = 0, then it’ll broadcast “remove sliders” and wait (if you don’t use broadcast and wait, it will not work), show the size variable, set slider to 2, wait 0.3 seconds and set it to 1. If slider = 1, it’ll broadcast “remove sliders”. If slider = 2, it’ll broadcast “remove sliders” and ask “size”. You can then just make it set the size variable to answer, but there’s more you can do. If answer = (blank, not space, just nothing), then it’ll do nothing. Else, if answer = D, set size to 5 (the default value). Else, set size to answer. When this sprite receives “remove sliders”, it’ll set slider to 0 and hide the size variable. Then, in everything else you can click (colour buttons, drawing canvas) (this is optional), make them broadcast “remove sliders” to automatically hide the variable when drawing or selecting.
Visual changes: Fix your spelling: “are you sure you want to delet everything?” “Whit 15 ”. Also update the instructions for the actual amount of colours. The more colours button is confusing, since a + doesn’t scream colour, so you can replace it with a colour wheel, palette, etc.
More features: Your project is titled “great draw”, but it ain’t great. Add more features, such as pen opacity (it may not work, but you can set pen opacity to 1 for blending/shading effects. Just so you know, the pen transparency block isn’t opacity, you have to do negative opacity + 100), line or box tool, spray tool, an entire particle engine with a lot of customisability… you can take inspiration. This isn’t an ad, but you should check out my drawing project, which has 10+ tools, advanced options, more and is still getting updated, which you can take inspiration from. If you do literally copy the code, make sure to credit.

From da shroom (I think I said too much)

ibrakhim123 wrote:

Hi

steindf2 wrote:

dosent work bc it only brodcasts it for like 0.1 sec

when I receive [Draw v]
pen down
wait until <not <mouse down?>>
pen up

steindf2 wrote:

and add a proper eraser mode that isn’t on a timer. If you want to keep it as the timer, make it more accurate with the use of a repeat 2 > move 0 steps (tells scratch to wait for 2 screen refreshes + 1 from the repeat until loop = 3 screen refreshes = 0.1 seconds) FIXED (partially) is finished

repeat (101)
repeat (2)
move (0) steps
end
change [eraser time v] by (-0.1)
end

you can make custom blocks les go ::motion cat
run without screen refresh{
repeat until <I can resize lists ::sensing>{
say to (Scratch Team v) [pls let mobile users resize lists] ::looks
}@loopArrow ::control
}::custom

ItsMushroomYt1104 wrote:

steindf2 wrote:

dosent work bc it only brodcasts it for like 0.1 sec

Wdym by that? I tried it and it works, so you might’ve done it wrong. Here’s the script:

when I receive [Draw v]
pen down
wait until <not <mouse down?>>
pen up

The message is broadcasted when the stage is clicked. The pen size setting and moving the pen blocks can be left in the forever loop.

steindf2 wrote:

and add a proper eraser mode that isn’t on a timer. If you want to keep it as the timer, make it more accurate with the use of a repeat 2 > move 0 steps (tells scratch to wait for 2 screen refreshes + 1 from the repeat until loop = 3 screen refreshes = 0.1 seconds) FIXED (partially) is finished

Now the timer counts way too fast. You put the change eraser time by -0.1 in the repeat 2 move 0 steps. It’s meant to be out of that, like this:

repeat (101)
repeat (2)
move (0) steps
end
change [eraser time v] by (-0.1)
end

Repeat 2 move 0 steps: waits for 2 screen refreshes (0.06666 67 seconds). Then, changes the eraser time by -0.1, then loops that, waiting 1 screen refresh before that (0.067 + 0.033 = 0.1 seconds). 0.1 x 101 = 10.1, making the eraser time stop at -0.1.

you can make custom blocks les go ::motion cat
run without screen refresh{
repeat until <I can resize lists ::sensing>{
say to (Scratch Team v) [pls let mobile users resize lists] ::looks
}@loopArrow ::control
}::custom

when [hello] key pressed
broadcast [ty for helping me so much] and wait
stop [this script]

steindf2 wrote:

ItsMushroomYt1104 wrote:

steindf2 wrote:

dosent work bc it only brodcasts it for like 0.1 sec

Wdym by that? I tried it and it works, so you might’ve done it wrong. Here’s the script:

when I receive [Draw v]
pen down
wait until <not <mouse down?>>
pen up

The message is broadcasted when the stage is clicked. The pen size setting and moving the pen blocks can be left in the forever loop.

steindf2 wrote:

and add a proper eraser mode that isn’t on a timer. If you want to keep it as the timer, make it more accurate with the use of a repeat 2 > move 0 steps (tells scratch to wait for 2 screen refreshes + 1 from the repeat until loop = 3 screen refreshes = 0.1 seconds) FIXED (partially) is finished

Now the timer counts way too fast. You put the change eraser time by -0.1 in the repeat 2 move 0 steps. It’s meant to be out of that, like this:

repeat (101)
repeat (2)
move (0) steps
end
change [eraser time v] by (-0.1)
end

Repeat 2 move 0 steps: waits for 2 screen refreshes (0.06666 67 seconds). Then, changes the eraser time by -0.1, then loops that, waiting 1 screen refresh before that (0.067 + 0.033 = 0.1 seconds). 0.1 x 101 = 10.1, making the eraser time stop at -0.1.

you can make custom blocks les go ::motion cat
run without screen refresh{
repeat until <I can resize lists ::sensing>{
say to (Scratch Team v) [pls let mobile users resize lists] ::looks
}@loopArrow ::control
}::custom

i think i fixed it now

steindf2 wrote:

when [hello] key pressed
broadcast [ty for helping me so much] and wait
stop [this script]

the fixy:

when [hello v] key pressed
broadcast (ty for helping me so much v) and wait
stop [this script v]

(::ring)oooh square block(::ring)::ring control
when [rotation acceleration v] > (10) ::motion hat
click @stopSign ::control
when @stopSign clicked ::events hat
say [oh no you stopped my project how could you] ::looks
what am I doing ::#f0abf7
well I can finally glow… :: #f6cdfa
AAAAA. :: #fef2ff
ok maybe that was a bit too much. ::#fff

ItsMushroomYt1104 wrote:

steindf2 wrote:

when [hello] key pressed
broadcast [ty for helping me so much] and wait
stop [this script]

the fixy:

when [hello v] key pressed
broadcast (ty for helping me so much v) and wait
stop [this script v]

(::ring)oooh square block(::ring)::ring control
when [rotation acceleration v] > (10) ::motion hat
click @stopSign ::control
when @stopSign clicked ::events hat
say [oh no you stopped my project how could you] ::looks
what am I doing ::#f0abf7
well I can finally glow… :: #f6cdfa
AAAAA. :: #fef2ff
ok maybe that was a bit too much. ::#fff

steindf2 wrote:

clicking the close button makes the pen continue drawing. Do you have any idea how to fix it ?

when stage clicked
broadcast (Draw v)

when flag clicked
forever
go to (mouse-pointer v)
set pen size to (the pen size variable whatever it’s called I don’t know so let’s do the Josh thing and make this variable name extremely long)
set pen colour to ((((red)*(65536))+((green)*(256)))+(blue)) ::pen //if it’s a custom colour (or you can make clicking the presets change RGB values)
when I receive [Draw v]
pen down
wait until <not<mouse down?>>
pen up

#bring back the cat blocks ::events cat
stop [doing things that… like… things that… it like… v]

steindf2 wrote:

random Websitewhen u are bored.

ItsMushroomYt1104 wrote:

steindf2 wrote:

clicking the close button makes the pen continue drawing. Do you have any idea how to fix it ?

In the backdrop:

when stage clicked
broadcast (Draw v)

In the pen sprite:

when flag clicked
forever
go to (mouse-pointer v)
set pen size to (the pen size variable whatever it’s called I don’t know so let’s do the Josh thing and make this variable name extremely long)
set pen colour to ((((red)*(65536))+((green)*(256)))+(blue)) ::pen //if it’s a custom colour (or you can make clicking the presets change RGB values)
when I receive [Draw v]
pen down
wait until <not<mouse down?>>
pen up

Random thingy:

#bring back the cat blocks ::events cat
stop [doing things that… like… things that… it like… v]

steindf2 wrote:

random Websitewhen u are bored.

So random. Imagine being a tube.

when green flag clicked
ask [how do you do the cat and the square] and wait
stop [ everything]
#bring back the cat blocks ::events cat
stop [ohh now i know v]

steindf2’s signature:

when i didint help you ignore this ::events cat
stop [check out steindf2 v] ::control cap

steindf2 wrote:

i already did this and it still does it

when I receive [loading end v]
forever{
if <mouse down?> then{
pen down
other stuffies ::custom
}else{
pen up
} ::control
} @loopArrow ::control cap

So you want me to stop checking you out now?

steindf2’s signature well only the second block:

[check out steindf2 v] ::obsolete stack

Here are some examples. The top is what you enter and bottom is the product.
motion ::motion
looks ::looks
sounds ::sound
events ::events
control ::control
sensing ::sensing
operators :colon operators (when I try to type it it becomes)
variables ::variables
lists ::list
my blocks ::custom
pen ::pen
video sensing ::video
say {Hi!}:colon obsolete (can’t type square brackets as well)

motion ::motion
looks ::looks
sounds ::sound
events ::events
control ::control
sensing ::sensing
operators ::operators
variables ::variables
list ::list
my blocks ::custom
pen ::pen
video sensing ::video
say [Hi!]::obsolete

bright pink ::#F0F
random colour ::#5E90AC

bright pink ::#F0F
random colour ::#5E90AC

block ::motion stack
this is a cap block ::control cap
weeks since 1900 ::sensing reporter
true ::boolean operators
(::ring)square block(::ring)::custom ring
when I do something ::events hat
mewo ::#C84 cat

block ::motion stack
this is a cap block ::control cap
weeks since 1900 ::sensing reporter
true ::boolean operators
(::ring)square block(::ring)::custom ring
when I do something ::events hat
mewo ::#C84 cat

so now the curly brackets are curly brackets
run this{
}and this{
You can put stuff here ::looks
}and also this{
}:colon operators
what is this {block{with another block{and another one} cause why not ::list} idk ::variables} ::events cat

run this{
}and this{
You can put stuff here ::looks
}and also this{
}::operators
what is this {block{with another block{and another one} cause why not ::list} idk ::variables} ::events cat

delete (10) clones ::control
say (this is what happens if you type text in round brackets) {so use square brackets} ::looks
these are (round v) and ::sensing cat
if <> then (#39AE1F) ::control reporter

delete (10) clones ::control
say (this is what happens if you type text in round brackets) [so use square brackets] ::looks
these are (round v) and [square v] ::sensing cat
if <> then (#39AE1F) ::control reporter

say \{this isn’t an input!} ::looks

say \[this isn’t an input!] ::looks

@greenFlag @loopArrow @addInput @delInput @turnLeft @turnRight ::grey

@greenFlag @loopArrow @addInput @delInput @turnLeft @turnRight ::grey

The loop arrow is always placed at the end of the block for some reason.