|Message: Re: /vis/scene/add/scale - only once per scale?||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)|
It looks like I've been a bit sloppy and not encoded the full list of parameters for distinguishing scale models. It is something I certainly meant to do. The following fixes it for me - hopefully also for you - and all being well it will make it into the next release. Just after instantiation of the scale model around line 2015 in G4VisCommandsSceneAdd.cc:
G4VModel* model = new G4ScaleModel(scale);
G4String globalDescription = model->GetGlobalDescription(); globalDescription += " (" + newValue + ")"; model->SetGlobalDescription(globalDescription);
You can see the models and their descriptions with /vis/scene/list and you can activate/de-activate with /vis/scene/activateModel.
Please also note that since this code was written we have made the scale and other visibles smarter and we no longer need to create the vis attributes on the heap, as written in some nearby comments. It's just that I forgot to improve the above code and fix the implied memory leak. So thanks also for leading me to this forgotten bit of code!!