|Message: Re: icsd extended example||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)|
Pedro Gomes writes: > In fact, in the main code I only found the line #include > "G4UIExecutive.hh". > > It is a bit strange that part of the application code is missing, > considering that it is an example provided in the Geant4-DNA with a > vis.mac macro file associated to it. I have not changed anything yet in > the example provided. Well, most of these extended examples develop by copy-and-paste evolution. I don't know why the vis lines would have been removed, but there's no reason you can't put them back :-) > I've looked at another examples provided in the Geant4-DNA where > visualization works fine and effectively that part of the code is not > missing at all. Yup. I checked mfp/mfp.cc, and the vis manager is there (with no preprocess protection). > Do you find the same error when you run this native example? Yes. If you don't create G4VisExecutive, you won't get any of the /vis UI commands. We have two versions of our own simulation executable, one with Vis (for interactive testing and pretty pictures), and one without (for batch running). If one of my users tries to run the detector drawing macro in batch, they get exactly the "command not found" failure. -- Mike Kelsey
|Inline Depth:||Outline Depth:||Add message:|