Hi, I think that pen is too slow.
Superfast draw blocks:

superfast line ()() - ()()  :: pen
superfast tri fill ()(), ()(), ()() :: pen
superfast quad fill ()(), ()(), ()(), ()() :: pen

You can put your code into a custom block and turn on “run without screen refresh”.

WindOctahedron wrote:

You can put your code into a custom block and turn on “run without screen refresh”.

Polygon fills require mutiple pen strokes.

Monniasza_spzoo wrote:

WindOctahedron wrote:

You can put your code into a custom block and turn on “run without screen refresh”.

Polygon fills require mutiple pen strokes.

Yes, they do. But you can use a loop to make these strokes, and “run without screen refresh” runs these loops without any delays and can draw a triangle in a couple of miliseconds or less.

So it would not use anti-aliasing to draw the lines and triangles and quadrilaterals? If so, this would definitely be useful for projects that update a single row or column at a time; the current pen tool doesn't work very well for this, as it produces artifacts as in ..

45afc4td wrote:

So it would not use anti-aliasing to draw the lines and triangles and quadrilaterals? If so, this would definitely be useful for projects that update a single row or column at a time; the current pen tool doesn't work very well for this, as it produces artifacts as in ..

It won't use antialiasing,

The “Run without screen refresh” option is the fastest possible option. The real fun part is optimizing it to render in the fastest possible way.

-Snipet- wrote:

The “Run without screen refresh” option is the fastest possible option. The real fun part is optimizing it to render in the fastest possible way.

When new blocks will be added, they will become fastest.

Also, in Scratch 3.0, a vertical pen line has blur to the left. So truly updating a single column requires updating everything to the left! As the superfast blocks won't use anti-aliasing, this won't be a problem for superfast rendering.

Monniasza_spzoo wrote:

-Snipet- wrote:

The “Run without screen refresh” option is the fastest possible option. The real fun part is optimizing it to render in the fastest possible way.

When new blocks will be added, they will become fastest.

But “Run without screen refresh” is already the fastest. Scratch is all about figuring out a way to put an idea down onto a computer. Tri and quad filling is just part of that. To learn, the ST purposely left out those features for users to make themselves. There are a ton of good fillers out there. While I do see where you’re going, I think Scratch code blocks should be like the alphabet: You can use letters to make words. Then those words go to make sentences. Those sentences make a paragraph, which multiple make a novel. Some blocks go to making simple algorithms, which make a poly filler, which make a game.

-Snipet- wrote:

Monniasza_spzoo wrote:

-Snipet- wrote:

The “Run without screen refresh” option is the fastest possible option. The real fun part is optimizing it to render in the fastest possible way.

When new blocks will be added, they will become fastest.

But “Run without screen refresh” is already the fastest. Scratch is all about figuring out a way to put an idea down onto a computer. Tri and quad filling is just part of that. To learn, the ST purposely left out those features for users to make themselves. There are a ton of good fillers out there. While I do see where you’re going, I think Scratch code blocks should be like the alphabet: You can use letters to make words. Then those words go to make sentences. Those sentences make a paragraph, which multiple make a novel. Some blocks go to making simple algorithms, which make a poly filler, which make a game.

The better idea would be making existing blocks faster for example compiling into GLSL and running multi-core and multi-threaded on GPU.

Monniasza_spzoo wrote:

-Snipet- wrote:

Monniasza_spzoo wrote:

-Snipet- wrote:

The “Run without screen refresh” option is the fastest possible option. The real fun part is optimizing it to render in the fastest possible way.

When new blocks will be added, they will become fastest.

But “Run without screen refresh” is already the fastest. Scratch is all about figuring out a way to put an idea down onto a computer. Tri and quad filling is just part of that. To learn, the ST purposely left out those features for users to make themselves. There are a ton of good fillers out there. While I do see where you’re going, I think Scratch code blocks should be like the alphabet: You can use letters to make words. Then those words go to make sentences. Those sentences make a paragraph, which multiple make a novel. Some blocks go to making simple algorithms, which make a poly filler, which make a game.

The better idea would be making existing blocks faster for example compiling into GLSL and running multi-core and multi-threaded on GPU.

So will this idea have anti-aliasing? The Scratch 3.0's line function is too blurry for https://scratch.mit.edu/projects/347110145/ to work properly.

WindOctahedron wrote:

You can put your code into a custom block and turn on “run without screen refresh”.

Yeah, that's pretty fast - I don't see why we would need a higher speed than that.