[Commit] papers/xr_ols2003 api.tex,1.12,1.13 appendix.tex,1.7,1.8
Carl Worth
commit@keithp.com
Fri, 16 May 2003 12:21:15 -0700
Committed by: cworth
Update of /local/src/CVS/papers/xr_ols2003
In directory home.keithp.com:/tmp/cvs-serv27091
Modified Files:
api.tex appendix.tex
Log Message:
Fixed placement of Hering figure
Index: api.tex
===================================================================
RCS file: /local/src/CVS/papers/xr_ols2003/api.tex,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- api.tex 16 May 2003 18:51:41 -0000 1.12
+++ api.tex 16 May 2003 19:21:12 -0000 1.13
@@ -67,9 +67,6 @@
bytes arranged as 4-byte ARGB pixels. A similar call,
XrSetTargetDrawable, is available to direct graphics to an X drawable.
-With the XrState object created and initialized with a rendering
-target, Xr is ready to accept drawing commands.
-
When the program is done using Xr, it signifies this by calling
XrDestroy. During XrDestroy, all data is released from the XrState
object. It is then invalid for the program to use the value of the
@@ -78,12 +75,6 @@
surface, and the program can access that surface as appropriate, (eg.
write the image to a file, display the graphics on the screen, etc.).
-Sections~\ref{sec:transformations}-\ref{sec:images} provide examples
-that build on this initial program. Each example consists of a single
-function that accepts an XrState pointer and performs drawing
-operations. Each example can be made into a complete program by simply
-adding the new function call to the program of Figure~\ref{fig:source_minimal}.
-
\subsection{Transformations}
\label{sec:transformations}
@@ -103,11 +94,6 @@
display pixel sizes of about 100 DPI, the pixel boundaries are still
significant.
-Initially, the CTM in Xr is an identity matrix, so user space will
-initially align with device space, (with the origin at the upper-left
-corner of the surface, the X axis increasing to the right, and the Y
-axis increasing down).
-
The CTM can be modified by the user to position, scale, or rotate
subsequent objects to be drawn. These operations are performed by the
functions XrTranslate, XrScale, and XrRotate. Additionally,
@@ -116,10 +102,6 @@
XrDefaultMatrix function can be used to restore the CTM to its
original state.
-In Figure~\ref{fig:hering}, each of the radial lines was drawn using
-identical path coordinates. The different angles were achieved by
-calling XrRotate before drawing each line. The source code for this
-image is in Figure~\ref{fig:hering_source}.
\begin{figure}[htbp]
\begin{center}
\epsfxsize=1in
@@ -128,6 +110,10 @@
\label{fig:hering}
\end{center}
\end{figure}
+In Figure~\ref{fig:hering}, each of the radial lines was drawn using
+identical path coordinates. The different angles were achieved by
+calling XrRotate before drawing each line. The source code for this
+image is in Figure~\ref{fig:hering_source}.
\subsection{Save/Restore of Graphics State}
Index: appendix.tex
===================================================================
RCS file: /local/src/CVS/papers/xr_ols2003/appendix.tex,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- appendix.tex 16 May 2003 15:39:14 -0000 1.7
+++ appendix.tex 16 May 2003 19:21:12 -0000 1.8
@@ -1,5 +1,12 @@
\appendix
+XXX: Fix this paragraph
+Sections~\ref{sec:transformations}-\ref{sec:images} provide examples
+that build on this initial program. Each example consists of a single
+function that accepts an XrState pointer and performs drawing
+operations. Each example can be made into a complete program by simply
+adding the new function call to the program of Figure~\ref{fig:source_minimal}.
+
\section{Example Source Code}
\begin{figure}[htbp]