What causes a console screen to shimmer

[Count23]

It costs less to do an if check than to clear the console screen and write more stuff to it does it not?

Not really, because if you're redrawing the whole screen and you've done it right, you concat your strings prior to writing it so you arent calling the screen:writestring() function so many times. Theoretically, if you've written your E2 right, you should only be callign screen:writestring() once per each line you need to write on the console screen.

[jacoby6000]

unless of course its displaying data with a progress bar and certain rows need different colors throughout them ^_^ but then again, you could always just use Cells i guess..

[Count23]

That's more of the exception then the rule, because you wouldnt be doing that very often on a text based screen, that's more something for the wired GPU. Not to mention the lag results for the screen/server trying to draw that kind of data, very fast (ie under 1 second), over and over again.

Altho, the smarter method for the progress bars in that instance would still be to concat your strings previously, draw them up as blank, write your "background" bar colour first, then write your "current progress" bar on top of the back one in a different colour, and redraw only those two lines each time your e2 updates.

Which is much less effort then writing a million writecell commands, and no worse then trying to write a writestring() for label and a writestring() for content.

[Schilcote]

Does the EGP do refresh-every-tick type stuff better?

On the increase in ops, does it really matter? So your E2 takes up 12% of the softquota instead of 11%. Big deal.

[Count23]

Does the EGP do refresh-every-tick type stuff better?

dunno what that is

On the increase in ops, does it really matter? So your E2 takes up 12% of the softquota instead of 11%. Big deal.

AFAIK the quota is shared among all your e2s, the more something like a console screen takes to process, the less you can allocate somewhere else.

[Schilcote]

The hardquota, which is all your E2s, is different from and higher than the softquota. And anyway, what are you doing that consumes the entire hardquota? Making fifty console screens work with their own chips?

[Dskodk]

timer("cscreen",1000)
if(clk("cscreen")){
console stuff
}

that does it for me.

[Count23]

The hardquota, which is all your E2s, is different from and higher than the softquota. And anyway, what are you doing that consumes the entire hardquota? Making fifty console screens work with their own chips?

Not so much, but its bad programming form to waste cycles. Not to mention that a lot of functions like advance hud indicators and the like tend to consume a fair amount of quota cycles too.

timer("cscreen",1000)
if(clk("cscreen")){
console stuff
}

that does it for me.

Interval(1000) with @triggers Time is easier, but thanks man.

[Divran]

Not so much, but its bad programming form to waste cycles..

It's also bad programming to write to the screen 100 times per second even if there are no changes for the user to see.

you mean a few if statements, don't you dirvan. Or has e2 finally got switch/case support?

Yes to both.

[Count23]

It's also bad programming to write to the screen 100 times per second even if there are no changes for the user to see..

Theoretically, that shouldnt be the case if you're using the "trigger" for inputs, rather then a timer, then your screen should only update on a new input.

Yes to both.

Any documentation on the switch syntax?