oh, btw: leero: that's a screen-buddy. There are plenty like that around - they react on icons and windows: the screensaver starts by taking a snapshot of your currect desktop, and going from there...
That's not what I was talking about. When I say a tiled background I mean using the tilesets built into OP2 and create randomly generated 'maps' out of them.
i know what u need to make a dynamic 3d screen saver. the way i know best uses flash. you get proggy called swift 3d, draw yur 3d model and import into swift which lets you put it in flash. but then you need another proggy that converts it into an executable but i cannot afford it.
Or you could just code a screensaver the way screensavers are coded.
SS's are essentially programs but they have two functions that are important: 1, the need the Options Dialogue wich is called through a specific funtion.
2, you need an entry-point funtion.
Most programs for Win32 would use WinMain, but Screen Savers have a different entry point.
I already have a fully-functioning refresh engine and I've done some preliminary testing to see if it would work for a screensaver and... it does! So it's a downright possibility for 3D screensavers... plus it's easy enough to generate scenes through code.
Moogle's idea of using OP2 as a shell would probably make the most sense. Starting a screen saver is easy enough. Once that's done you can pretty much do what any program does so having the Config dialogue point to the OP2 directory and define a screen resolution and then having the entry-point function set a resolution and use OP2's internal commands and whatnot seems completely feasible.
How to use and what the OP2 funtions are is a mystery to me but I can do the screensaver general programming.
