[BasicCasio] Code Optimization

[Vladadamm]

So, i did a simple program on my Casio in maths today that colors one pixel on 2 on the screen in that scheme :

010101010
101010101
010101010
101010101
010101010

(1 being colored pixels and 0 blank pixels).

My current problem is that the program takes a long time to do the whole screen, and so i would like to fasten it a bit if there's any way to optimize the code.

Code

//Graphics Parameters
ViewWindow 1, 127, 0, 1, 63, 0
AxesOff
GridOff
LabelOff
//Grid Creation
2->A
1->B
While B=!64
PxlOn B,A
If A<125
Then A+2->A
Else A-125->A
B+1->B
IfEnd
WhileEnd
//Keeping the grid on the screen until Exe is pressed
While Getkey=!31
WhileEnd
//Resetting Graphics Parameters, Variables & such to default
Prog "INITCONF"

With that code, it takes a few minutes to have the grid on the whole screen, and that's quite a problem. So i'm searching ways to make it faster if it's possible. So, hmm any ideas ?

 

[Dr Super Good]

I am guessing it draws each pixel 1 at a time and waits for the display to refresh. As such it takes approximately 4,000 frames to build the graphic.

If there is some way you can disable graphic display until the graphic is complete (a back buffer) that could speed it up. The idea is you generate the graphic and only display it when it is complete saving time updating for each pixel.

Another way would be to generate it using diagonal lines. Instead of 4000 individual pixels, you use about 128 individual lines at a diagonal, each filling in many pixels. As each line probably takes a frame or two to draw it will be much faster compared to the individual pixels.

 

[Statharas]

That's just situational. He's looking for a more optimized way in general.

 

[Dr Super Good]

He's looking for a more optimized way in general.

What do you mean by "in general"? How does what I said not make graphic rendering faster in most cases?

 

[Statharas]

As in, painting all pixels faster. What if he wants only vertical lines to be painted? Or horizontal?

 

[Dr Super Good]

Preventing the display from refreshing will still be faster as the cost seems to be related to that. It has to refresh the display after drawing every pixel.

If this is the case, then sending line draw commands instead of pixel draw commands will also be faster as each may fill many pixels in a single frame.

 

[Vladadamm]

Preventing the display from refreshing will still be faster as the cost seems to be related to that. It has to refresh the display after drawing every pixel.

If this is the case, then sending line draw commands instead of pixel draw commands will also be faster as each may fill many pixels in a single frame.

Well, tested with the window being created after the grid is created, it doesn't seems to fasten it.

Diagonal lines fasten it a lot, but too lazy to find a good algorithm that works well with those atm (just tested with drawing 50 diagonal lines).

Else, I've fund another way to do it using representative curves :

Graph Y>1

This only takes ~1 seconds to do it.

 

[Dr Super Good]

What is the full code you are using that does it so fast? Or are you using the calculator's graphic function with an appropriate equation?

 

[Vladadamm]

What is the full code you are using that does it so fast? Or are you using the calculator's graphic function with an appropriate equation?

It's graphic function.

Else, it's only the Grid creation that changed, the rest is the same.