function lunch (x, y : real) : real
result 400 * sind (x / (sin (y) * 10)) + (sin (3 * y + 1) * 1800 * sind (x / 5 + 80))
%result (x / 10) ** 3
end lunch


View.Set ("offscreenonly")
var delta := 1
var min_x, min_y, max_x, max_y, y, ax, ay, px, py, ox, oy, dy, dx : real
var ft := true



min_x := -2000
min_y := -5000
max_x := 1000
max_y := 5000

dx := 20
dy := 20

ox := (-min_x) * (maxx / (max_x - min_x))
oy := (-min_y) * (maxy / (max_y - min_y))
var x := min_x



procedure graphfunction (aj : function func (x, y : real) : real, f : real, c : int)
var slope : real
x := min_x - 400
ft := true
var counter : int := 0
loop
counter := counter + 1
x += delta
y := aj (x, f)
exit when x >= max_x + 400


ax := ((x * ((maxx / (max_x - min_x)))) + (ox))
ay := (y * (maxy / (max_y - min_y))) + (oy) %round (max_y * (maxy / (max_y - min_y)))
if not ft then
drawline (round (ax), round (ay), round (px), round (py), c)
if ((counter * delta) mod 10) = 0 then
drawline (round (ax), round (ay), round (ax + (- (py - ay) * (1500 / delta))), round (ay + ((px - ax) * (1500 / delta))), c)
drawline (round (ax), round (ay), round (ax + ((py - ay) * (1500 / delta))), round (ay + (- (px - ax) * (1500 / delta))), 155 - c)
end if
else
ft := false
end if
px := ax
py := ay

end loop
end graphfunction







color (white)
colorback (black)
cls
var xi : real := ox
var yi : real := oy
var r : real := 1
loop
r += .01
graphfunction (lunch, r, round ((r * 10) mod 155))
View.Update
cls
end loop

That's pretty cool, I wish I could make it my screen saver. But doesn't this fall under the "omfg sooo trippy cool flashes!" category?

function lunch (x, y : real) : real
%result 400 * sind (x / (sin (y) * 10)) + (sin (4 * y + 1) * 1800 * sind (x / 5 + 80))
result (x / (10 / y)) ** 2
/*if x = 0 then
result 1000000
else
result y * 50000 / (x )
end if*/
end lunch


View.Set ("offscreenonly")
var delta := 1
var min_x, min_y, max_x, max_y, y, ax, ay, px, py, ox, oy, dy, dx : real
var ft := true



min_x := -1000
min_y := -5000
max_x := 1000
max_y := 10000

dx := 20
dy := 20

ox := (-min_x) * (maxx / (max_x - min_x))
oy := (-min_y) * (maxy / (max_y - min_y))
var x := min_x



procedure graphfunction (aj : function func (x, y : real) : real, f : real, c : int)
var slope : real
x := min_x - 400
ft := true
var counter : int := 0
loop
counter := counter + 1
x += delta
y := aj (x, f)
exit when x >= max_x + 400


ax := ((x * ((maxx / (max_x - min_x)))) + (ox))
ay := (y * (maxy / (max_y - min_y))) + (oy) %round (max_y * (maxy / (max_y - min_y)))
if not ft then
drawline (round (ax), round (ay), round (px), round (py), c)
if ((counter * delta) mod 10) = 0 then
drawline (round (ax), round (ay), round (ax + (- (py - ay) * (1500 / delta))), round (ay + ((px - ax) * (1500 / delta))), c)
drawline (round (ax), round (ay), round (ax + ((py - ay) * (1500 / delta))), round (ay + (- (px - ax) * (1500 / delta))), 155 - c)
end if
else
ft := false
end if
px := ax
py := ay

end loop
end graphfunction







color (white)
colorback (black)
cls
var xi : real := ox
var yi : real := oy
var r : real := 1
loop
r += .01
graphfunction (lunch, r, round ((r * 10) mod 155))
View.Update
delay (10)
cls
end loop

No. The original reason for screensavers is because of an effect called "burn-in" that occurs in CRT monitors, which were used almost exclusively until about 10 years ago. The problem is that if the CRT displays the same image for too long, the phosphors in the screen are actually permanently changed, leaving a "ghost" of that image. Because people have a bad habit of walking away from their computers without turning off the screens, the screensaver is designed to automatically start after a few minutes of inactivity.

The screensaver works by making the screen display a constantly-changing set of images, preventing any particular image from burning into the screen.

Although some modern screen types still suffer from burn-in (notably not LCDs), screensavers are largely aesthetic now.

A Turing "screensaver", if properly constructed so that the whole image changes, shouldn't damage your screen. If, however, only part of the image changes while other parts do not (for example, if the window area changes but the title bar at the top does not, then the title bar could burn in.

@andrew and @copthesaint : Ouch..