Near future plans of Run Category

G4ApplicationState

main()

Overview of user action classes

Individual details of each action classes

Solutions :

• Just forget it.
• "One way"
• "Interactive"
  • Introduce G4PickingManager which communicates with Vis
  • Show information with “level of detail”
  • Concrete classes of G4VPickingMessenger

Time scale:

• Just forget it.
• "One way"
  • Minor modifications in Vis
  • Available by the beta-release
• “Interactive”
  • Should be provided by “Plug In”
  • No modification needed in G4 kernel
  • Long term plan

“State sensitive” command

Treatments of the default value

• G4UIparameter::SetDefaultValue method
• Introducing G4UIparameter::currentValueAsDefault(G4bool)
• You need to supply GetCurrentValue method.

Solutions :

• Just forget it.
• "One way"
  • Send all information by character strings while drawing
  • Display information associated with a picked object
  • Picking is encapsulated in Vis
  • No call-back to G4 kernel

Destruct your G4UImessenger concrete class by yourself when the target (addressed) class is deleted.

• Write delete operator in the destructor of your target class.

Delete G4UIcommand objects you defined when the messenger is deleted.

• Write delete operators in the destructor of your concrete messenger.
• You need not to delete parameters.

More levels of abstract classes for messenger.

• e.g. G4UImessengerWithAnInteger, etc.

More methods in abstract messenger.

• e.g. SetNewValues(G4UIcommand*, G4int)

“Range check” to the given parameter value.

• “C++ like” condition(s) x > 0. && x < 10.
• Candidate list

“Type check” to the parameter

• Allowed types : i, d, s, b