14 .TH XScreenSaver 1 "12-Nov-99 (3.20)" "X Version 11"
16 xscreensaver-demo - interactively control the background xscreensaver daemon
19 [\-display \fIhost:display.screen\fP] [\-prefs] [\-xrm \fIresources\fP]
21 The \fIxscreensaver\-demo\fP program is a graphical front-end for
22 setting the parameters used by the background
25 It is essentially two things: a tool for editing the \fI~/.xscreensaver\fP
26 file; and a tool for demoing the various graphics hacks that
27 the \fIxscreensaver\fP daemon will launch.
30 this manual describes the Gtk version of the \fIxscreensaver\-demo\fP
31 command. The UI of the Motif and Athena versions of \fIxscreensaver\-demo\fP
32 is a bit different (for now.)
34 The main window consists of a menu bar and two tabbed pages. The first page
35 is for editing the list of demos, and the second is for editing various other
36 parameters of the screensaver.
38 All of these commands are on either the \fBFile\fP or \fBHelp\fP menus:
41 Activates the background \fIxscreensaver\fP daemon, which will then run
42 a demo at random. This is the same as running
43 .BR xscreensaver-command (1)
44 with the \fI\-activate\fP option.
47 Just like \fBBlank Screen Now\fP, except the screen will be locked as
48 well (even if it is not configured to lock all the time.) This is the
50 .BR xscreensaver-command (1)
51 with the \fI\-lock\fP option.
54 If the xscreensaver daemon is running on this screen, kill it.
55 This is the same as running
56 .BR xscreensaver-command (1)
57 with the \fI\-exit\fP option.
60 If the xscreensaver daemon is running on this screen, kill it.
61 Then launch it again. This is the same as doing
62 ``\fIxscreensaver-command -exit\fP'' followed by ``\fIxscreensaver\fP''.
64 Note that it is \fInot\fP the same as doing
65 ``\fIxscreensaver-command -restart\fP''.
68 Exits the \fIxscreensaver-demo\fP program (this program) without
69 affecting the background \fIxscreensaver\fP daemon, if any.
72 Displays the version number of this program, \fIxscreensaver-demo\fP.
75 Opens up a web browser looking at the XScreenSaver web page, where you
76 can find online copies of the
78 .BR xscreensaver\-demo (1),
80 .BR xscreensaver\-command (1)
82 .SH GRAPHICS DEMOS TAB
83 On the left is a list of the names of the various display modes, and
84 on the right are some fields that let you edit their behavior.
87 Double-clicking in the list on the left will let you try out the indicated
88 demo. The screen will go black, and the program will run in full-screen
89 mode, just as it would if the \fIxscreensaver\fP daemon had launched it.
90 Clicking the mouse again will stop the demo and un-blank the screen, making
91 the dialog box visible again.
93 Single-clicking in the list will populate the fields on the right side of
97 Beneath the list are a pair of up and down arrows. Clicking on the down
98 arrow will select the next item in the list, and then run it in full-screen
99 mode, just as if you had double-clicked on it. The up arrow goes the other
100 way. This is just a shortcut for trying out all of the display modes in turn.
102 .B Program Description
103 At the top will be a brief description of the program. Below that is a
104 text field where you can edit the arguments to the program as xscreensaver
105 will invoke it. (Note that most of these programs have their own man pages
106 that describe the command-line options they take.)
109 The \fIEnabled\fI checkbox controls whether xscreensaver will use this
110 display mode at all. This way, all the modes can remain available, but
111 you can choose which ones will be automatically run.
114 The \fIVisual\fI field is where you can select the X visual type that this
115 demo will require. If you specify one (other than \fIAny\fP) then the
116 program will only be run on that kind of visual. For example, you can
117 specify that a particular program should only be run if color is available,
118 and another should only be run in monochrome. See the discussion of the
119 \fIprograms\fP parameter in the \fIConfiguration\fP section of the
123 This is a combo-box, so you can either select an item from the popup menu,
124 or type in a specific visual's hexadecimal ID.
127 This button saves your changes and runs the demo in full-screen mode so
128 that you can try it out. Click the mouse to dismiss it.
131 This button saves your changes to your \fI~/.xscreensaver\fP file,
137 This button discards any unsaved changes you have made, and reverts the
138 settings for the selected demo back to what they were before. Note that
139 once you hit \fIDemo\fP or \fIApply\fP, that's it!
140 .SH SCREENSAVER OPTIONS TAB
141 This tab lets you change various settings used by the xscreensaver daemon
142 itself, rather than its sub-programs.
145 After the user has been idle this long, the \fIxscreensaver\fP daemon
146 will blank the screen.
149 After the screensaver has been running for this long, the currently
150 running graphics demo will be killed, and a new one started.
151 If this is 0, then the graphics demo will never be changed:
152 only one demo will run until the screensaver is deactivated by user
156 Whether to print lots of debugging information.
159 Whether to install a private colormap while the screensaver is active, so
160 that the graphics hacks can get as many colors as possible. (This only
161 applies when the screen's default visual is being used, since non-default
162 visuals get their own colormaps automatically.) This can also be overridden
166 If selected, then when the screensaver activates, the current contents
167 of the screen will fade to black instead of simply winking out. This only
168 works on displays with writable colormaps, that is, if the screen's default
169 visual is a PseudoColor visual. A fade will also be done when
170 switching graphics hacks (when the \fICycle Timeout\fP expires.)
173 The complement to \fIFade Colormap\fP: if selected, then when the screensaver
174 deactivates, the original contents of the screen will fade in from black
175 instead of appearing immediately. This only works on displays with writable
176 colormaps, and when \fIFade Colormap\fP is also selected.
179 When fading or unfading are selected, this controls how long the fade will
183 This controls how many times a second the colormap will be changed to
184 effect a fade. Higher numbers yield smoother fades, but may make the
185 fades take longer than the specified number of seconds, if your server
186 isn't fast enough to keep up.
189 Whether the screen saver should lock the screen when it activates.
192 If \fIRequire Password\fP is selected, this controls the length of
193 the ``grace period'' between when the screensaver activates, and when the
194 screen becomes locked. For example, if this is 0:05:00,
195 and \fISaver Timeout\fP is 0:10:00, then after 10 minutes, the screen
196 would blank. If there was user activity at 12 minutes, no password
197 would be required to un-blank the screen. But, if there was user activity
198 at 15 minutes or later (that is, \fILock Timeout\fP minutes after
199 activation) then a password would be required. The default is 0, meaning
200 that if locking is enabled, then a password will be required as soon as the
204 When the screensaver is prompting for a password, the prompt dialog box will
205 stay on the screen for this long before giving up, and reverting to
208 There are more settings than these available, but these are the most
209 commonly used ones; see the manual for
211 for other parameters that can be set by editing the \fI~/.xscreensaver\fP
212 file, or the X resource database.
213 .SH COMMAND-LINE OPTIONS
214 .I xscreensaver\-demo
215 accepts the following command line options.
217 .B \-display \fIhost:display.screen\fP
218 The X display to use. The \fIxscreensaver\-demo\fP program will open its
219 window on that display, and also control the \fIxscreensaver\fP daemon that
220 is managing that same display.
223 Start up with the \fBScreensaver Options\fP tab selected by default
224 instead of the \fBGraphics Demos\fP tab.
226 It is important that the \fIxscreensaver\fP and \fIxscreensaver\-demo\fP
227 processes be running on the same machine, or at least, on two machines
228 that share a file system. When \fIxscreensaver\-demo\fP writes a new version
229 of the \fI~/.xscreensaver\fP file, it's important that the \fIxscreensaver\fP
230 see that same file. If the two processes are seeing
231 different \fI~/.xscreensaver\fP files, things will malfunction.
236 to get the default host and display number.
239 to find the sub-programs to run. However, note that the sub-programs
240 are actually launched by the \fIxscreensaver\fP daemon, not
241 by \fIxscreensaver-demo\fP itself. So, what matters is what \fB$PATH\fP
242 the \fIxscreensaver\fP program sees.
245 for the directory in which to read and write the \fI.xscreensaver\fP file.
248 to get the name of a resource file that overrides the global resources
249 stored in the RESOURCE_MANAGER property.
251 The latest version can always be found at
252 http://www.jwz.org/xscreensaver/
255 .BR xscreensaver (1),
256 .BR xscreensaver\-command (1)
258 Copyright \(co 1992, 1993, 1997, 1998, 1999
259 by Jamie Zawinski. Permission to use, copy, modify, distribute, and sell
260 this software and its documentation for any purpose is hereby granted without
261 fee, provided that the above copyright notice appear in all copies and that
262 both that copyright notice and this permission notice appear in supporting
263 documentation. No representations are made about the suitability of this
264 software for any purpose. It is provided "as is" without express or implied
267 Jamie Zawinski <jwz@jwz.org>, 13-aug-92.
269 Please let me know if you find any bugs or make any improvements.
projects / xscreensaver / blob