Using the custom propagator in the detector simulation

Now using the custom propagator in the detector simulation: one step forward to solve issue #1 (closed) .

Removed the forward declaration of TFRPropagator and TFRGeometry: is it really needed to have TFRPropagator as member of TFRGeometry? Cross-inclusions and linking (as well forward declarations) must be used only in really specific cases, since they are not optimal.

Setting of the tracks in the detector_sim.

include/TFRGeometry.cpp

@@ -4,7 +4,6 @@
  */
 
 #include "TFRGeometry.h"
-#include "TFRPropagator.h"
 
 //------------
 // Constructor
@@ -14,9 +13,9 @@ TFRGeometry::TFRGeometry(const std::string configFile_name){
   //-------------------------------//
   // setup the default propagator  //
   //-------------------------------//
-  
+
+  /*
   propagator = new TEveTrackPropagator();
-  propagator_own = new TFRPropagator(this);
   
   //setup the Runge Kutta stepper
   propagator->SetStepper(TEveTrackPropagator::kRungeKutta);
@@ -29,6 +28,7 @@ TFRGeometry::TFRGeometry(const std::string configFile_name){
   propagator->SetMaxZ(1000.);               //maximum z-coordinate to propagate, cm
   propagator->SetMaxR(100000000);           //maximum bending radius to propagate, cm
   propagator->SetDelta(pow(10., -6.));      //'error' on trajectory reconstruction
+  */
   
   //-----------------------------------------------//
   //  set the geometry from the input config file  //