Changeset 1208 for trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/enhanceddrawing.xml

Timestamp:

Nov 30, 2009, 3:52:24 PM (15 years ago)

Author:

garnier

Message:

CVS update

Location:

trunk/documents/UserDoc

Files:

• . (modified) (1 prop)
• DocBookUsersGuides (modified) (1 prop)
• DocBookUsersGuides/ForApplicationDeveloper (modified) (1 prop)
• DocBookUsersGuides/ForApplicationDeveloper/xml (modified) (1 prop)
• DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization (modified) (1 prop)
• DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/enhanceddrawing.xml (modified) (6 diffs)

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/enhanceddrawing.xml

@@ -81 +81 @@
       </entry>
       <entry>
-        0
+        2 pixels or mm*
+      </entry>
+    </row>
+    <row>
+      <entry>
+        Auxiliary point size type
+      </entry>
+      <entry>
+        screen
       </entry>
     </row>
@@ -129 +137 @@
       </entry>
       <entry>
-        0
+        2 pixels or mm*
+      </entry>
+    </row>
+    <row>
+      <entry>
+        Step point size type
+      </entry>
+      <entry>
+        screen
       </entry>
     </row>
@@ -167 +183 @@
   </tgroup>
 </informaltable>
+</para>
+
+<para>
+* Depending on size type.  If size type == screen, pixels are assumed and no unit need be supplied.  If size type == world, a unit must be supplied, e.g., 10 cm.
 </para>
 
@@ -176 +196 @@
     The context approach is intended to replace the configuration
     through the imode parameter. The use of imode is depreciated and
-    will be removed in Geant4 v9.0.
+    will be removed in Geant4 v10.0.
   </para></listitem>
   <listitem><para>
@@ -581 +601 @@
 
 <para>
-To draw by time, you need to use a trajectory that records the
-track time at the beginning and end of each step. To do this, write
-a tracking action that sets G4RichTrajectory, for example:
-
-<informalexample>
-<programlisting>
-#include "G4UserTrackingAction.hh"
-class G4Track;
-class MyTrackingAction : public G4UserTrackingAction
-{
-   public:
-   virtual void PreUserTrackingAction(const G4Track* aTrack);
-};
-#include "G4RichTrajectory.hh"
-#include "G4TrackingManager.hh"
-#include "G4IdentityTrajectoryFilter.hh"
-#include "G4TransportationManager.hh"
-#include "G4PropagatorInField.hh"
-void MyTrackingAction::PreUserTrackingAction(const G4Track* aTrack)
-{
-  // Require rich trajectory...
-  fpTrackingManager-&gt;SetTrajectory(new G4RichTrajectory(aTrack));
-
-  // Activate storing of auxiliary points for smoother trajectory...
-  static G4IdentityTrajectoryFilter curvedFilter;
-  G4TransportationManager::GetTransportationManager()-&gt;
-    GetPropagatorInField()-&gt;SetTrajectoryFilter(&amp;curvedFilter);
-}
-</programlisting>
-</informalexample>
-
-and register an instance of this with the run manager (this can be
-done once and for all as soon as the run manager is instantiated,
-probably in your main program):
-
-<informalexample>
-<programlisting>
-#include "MyTrackingAction.hh"
-...
-  runManager -&gt; SetUserAction (new MyTrackingAction);
+To draw by time, you need to use G4RichTrajectory, for example:
+
+<informalexample>
+<programlisting>
+/vis/scene/add/trajectories rich
+</programlisting>
+</informalexample>
+
+or
+
+<informalexample>
+<programlisting>
+/vis/scene/add/trajectories rich smooth
 </programlisting>
 </informalexample>
@@ -648 +641 @@
 /vis/open OGLSX
 /vis/drawVolume
-/vis/scene/add/trajectories
+/vis/scene/add/trajectories rich
 /vis/ogl/set/startTime 0.5 ns
 /vis/ogl/set/endTime 0.8 ns