2003-05-13 18:55:07 +00:00
|
|
|
<h2>Screensaver/core/app interaction (graphics)</h2>
|
|
|
|
|
|
|
|
TO BE WRITTEN
|
|
|
|
|
|
|
|
<p>
|
2003-05-20 00:03:39 +00:00
|
|
|
The graphics API uses a file <b>graphics.xml</b>
|
|
|
|
that is created and occasionally modified by the
|
|
|
|
core client or screensaver.
|
|
|
|
This file has the format
|
|
|
|
<pre>
|
|
|
|
<graphics_info>
|
|
|
|
<do_graphics/>
|
|
|
|
<xsize>500</xsize>
|
|
|
|
<ysize>400</ysize>
|
|
|
|
<full_screen/>
|
|
|
|
</graphics_info>
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
The graphics API implementation uses a 60 Hz timer.
|
|
|
|
Every 0.5 sec, it sees if graphics.xml has been modified, and if so parses it.
|
|
|
|
Every 1/60 sec, it sees if it's time for a new frame,
|
|
|
|
and if so calls <tt>app_render()</tt>.
|
2003-05-13 18:55:07 +00:00
|
|
|
<p>
|
|
|
|
Explain graphics modes of apps
|
|
|
|
<p>
|
|
|
|
Explain graphics use of shmem
|
|
|
|
<p>
|
|
|
|
Explain screensaver module
|
|
|
|
<p>
|
|
|
|
Explain screensaver logic in core
|