|Message: SegV in PreUserTrackingAction due to missing Touchable.||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Makoto Asai writes: > In your PostUserTrackingAction() method, you can invoke > G4TrackingManager::SetStoreTrajectory(false). > In case a trajectory for this particular track has been made, > it is pruned. Don't forget to reset SetStoreTrajectory(true) > in your PreUserTrackingAction() for next track. Thanks for this, but it leads me to a problem: The code I'm working on has custom subclasses of G4TrackingAction, G4Trajectory and G4TrajectoryPoint. They are written here with names lacking the "G4" prefix. In TrackingAction::PreUserTrackingAction() a Trajectory is created and in the process, G4Track::GetVelocity() is called in order to set the the initial TrajectoryPoint's velocity. (This is the correct procedure, right?). When this sequence is executed for opticalphotons it leads to a SegV. I have traced the SegV to the apparent fact that there is no Touchable associated with the G4Track at the time PreUserTrackingAction() is called. This leads to the SegV as G4Track::GetVelocity() accesses the Touchable in order to get the RINDEX of the material. In G4TrackingManager I find that indeed the PreUserTrackingAction() is called just before G4SteppingManager::SetInitialStep, and it is this latter method which sets the G4Track's touchable. This is using 4.5.2. Is this a real G4 bug, or is it possible I have done something wrong? Thanks, -Brett.
|Inline Depth:||Outline Depth:||Add message:|