summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/pst-solides3d/doc-en/par-nommersolide_en_corr.tex
blob: f744dc9c7f85ed882896204b19da0bb658f58b6b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
\section{Naming a solid}

For certain purposes, it is helpful to save a solid in working
storage to allow it to be referenced later on. To do so, we
activate the Boolean \verb+solidmemory+, which allows the
transmission of a variable throughout the code.

Consequently, activation of this Boolean deactivates drawing
by the macros \bs{psSolid}, \bs{psSurface} and \bs{psProjection}
immediate. To obtain the drawing, we use the macro
\verb+\composeSolid+ at the end of the code.

When \verb+\psset{solidmemory}+ is set up, we can use the option
\verb+[name=...]+ of the macro \bs{psSolid}.

In the example below, a coloured solid is constructed, which is
named $A$. It is drawn using the object \verb+[object=cube]+ with
the parameter \texttt{[load=$A$]}.

Note that \verb+linecolor=blue+, used while constructing our cube,
has no effect on the drawing: only the structure of the solid is
stored (vertices, faces, colours of faces), not the thickness of
any line, nor its colour, nor the position of the light source.
The settings of those parameters are taken into account at the
time the solid is rendered.


Finally, we demonstrate the use of the option
\verb+[deactivatecolor]+ which allows the cube to keep its
original red colour (otherwise the default colours would be used
within the object \verb+load+).

\psset{lightsrc=10 0 10,viewpoint=50 -20 10 rtp2xyz,Decran=50}
\begin{LTXexample}[width=6.5cm]
\psset{unit=0.75}
\begin{pspicture*}(-4,-4)(5,4)
\psset{solidmemory}
\psSolid[object=cube,
      linecolor=blue,
      a=4,fillcolor=red!50,
      ngrid=3,
      action=none,
      name=A,
      ](0,0,0)
\psSolid[object=load,
   deactivatecolor,
   load=A]
\composeSolid
\end{pspicture*}
\end{LTXexample}

With the option \verb+solidmemory+, the names of variables are
relatively well encapsulated, and there will be no conflict with
the variables of the dvips driver. There remains however the risk
of a collision with the names used in the \texttt{solides.pro}
file. You could use only single letter variable names, for
example, and it is necessary to avoid names like \verb+vecteur+,
\verb+distance+, \verb+droite+, etc. which are already defined in
the package.


\endinput