[svn-upgrade] Integrating new upstream version, ion3 (20070203)

[ion3-doc.git] / conf-winprops.tex

diff --git a/conf-winprops.tex b/conf-winprops.tex
index 10c1c10fa8b3d4bc4ddf8485b4d9285ebe66c5cb..9a416d3ec0c20bf50db277185d25f23067e2d0c5 100644 (file)
--- a/conf-winprops.tex
+++ b/conf-winprops.tex
@@ -100,12 +100,32 @@ usual method of identifying windows, and how to obtain this information.
 \end{winprop}
 
 
+\begin{winprop}{new_group}{string}
+    \index{new-group@\var{new_group}}
+    If the region specified by \code{target} winprop does not exist
+    (or that winprop is not set), create a new workspace using the 
+    previously stored layout (see \fnref{ioncore.deflayout}) named by
+    this property. After creating the workspace, \code{target} is 
+    attempted to be found again. (If that still fails, the newly 
+    created workspace is still asked to manage the client window.)
+\end{winprop}
+
+
 \begin{winprop}{oneshot}{boolean}
     \index{oneshot@\var{oneshot}}
     Discard this winprop after first use. 
 \end{winprop}
 
 
+\begin{winprop}{statusbar}{string}
+    \index{statusbar@\var{statusbar}}
+    Put the window on the statusbar, in the named tray component,
+    (The default tray component is called simply ``\code{systray}'', 
+    and others you give names to in your custom template, always 
+    prefixed by ``\code{systray_}''.
+\end{winprop}
+
+
 \begin{winprop}{switchto}{boolean}
     \index{switchto@\var{switchto}}
     Should a newly mapped client window be switched to within
@@ -116,7 +136,7 @@ usual method of identifying windows, and how to obtain this information.
 \begin{winprop}{target}{string}
     \index{target@\var{target}}
     The name of an object (workspace, frame) that should manage 
-    windows of this type. 
+    windows of this type. See also \code{new_group}.
 \end{winprop}