|Message: Re: Final step information for parent particle||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)|
Probably what you need to do is implement your own G4UserSteppingAction, G4UserEventAction, and G4UserTrackingAction. Common to all implement a std::vector<G4Track>. In BeginOfEventAction() clear the vector (deleting contents). In PostUserTrackingAction() save a COPY of the track into the vector (the G4 kernel will be deleting its G4Event, so you need a copy). If you need stepping variables other than just the track, do that in UserSteppingAction().
Now whenever you need information about the final step of a track, search your vector for the track you need. This must happen before the end of the event as the beginning of the next event will delete this information (and track IDs will be re-used).
NOTE: Due to the design of the user classes, you cannot derive a single class of your own from all 3 G4 user classes, because if you do that it will be deleted multiple times. I wrote my own class with all the required functions, and then wrote three simple helper classes that just call the routines of my class; each helper class implements just one G4 user interface so there are no multiple deletes. I must of course delete my class instance myself (or not bother, as there's really no need to delete stuff when exit() is about to be called). There must be just a single instance of all these classes.
|Inline Depth:||Outline Depth:||Add message:|