|Message: Re: Processing order||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)|
Thank you for your explanation. There is something I don't have clear, something I do not have the right feeling for yet. For example, either to check if the particle was killed by leaving the the universe or by an inelastic process, I can do it in the UsrSteppingAction. If I want to transfer information from this particle before it gets killed to the secondaries, Could I do this in the PostUserTrackingAction()? So it is safe to assume secondaries are generated and loaded into the stack before the parent ID gets completely killed. In that case, I could use the aTrack object of PostUserTrackingAction(G4Track *aTrack) to do what I want, right?
They do that in TestEm07... but I am not totally sure exactly how the killing process gets handle.
|Inline Depth:||Outline Depth:||Add message:|