Loading...
Searching...
No Matches
QT Dialogs
Visualisation

## Classes

class | BALL::VIEW::AmberConfigurationDialog
class | BALL::VIEW::AssignBondOrderConfigurationDialog
class | BALL::VIEW::AtomOverview
class | BALL::VIEW::BondProperties
class | BALL::VIEW::CharmmConfigurationDialog
class | BALL::VIEW::ClippingDialog
class | BALL::VIEW::ColoringSettingsDialog
class | BALL::VIEW::CompositeProperties
class | BALL::VIEW::ContourSurfaceDialog
class | BALL::VIEW::DisplayProperties
class | BALL::VIEW::DockDialog
class | BALL::VIEW::DockProgressDialog
class | BALL::VIEW::DockResultDialog
class | BALL::VIEW::DownloadElectronDensity
class | BALL::VIEW::DownloadPDBFile
class | BALL::VIEW::EditSettings
class | BALL::VIEW::FDPBDialog
class | BALL::VIEW::FieldLinesDialog
class | BALL::VIEW::GenerateCrystalDialog
class | BALL::VIEW::GeometricFitDialog
class | BALL::VIEW::GridVisualizationDialog
class | BALL::VIEW::LabelDialog
class | BALL::VIEW::LightSettings
class | BALL::VIEW::MainControlPreferences
class | BALL::VIEW::MaterialSettings
class | BALL::VIEW::MinimizationDialog
class | BALL::VIEW::MMFF94ConfigurationDialog
class | BALL::VIEW::ModelSettingsDialog
class | BALL::VIEW::ModifyRepresentationDialog
class | BALL::VIEW::MolecularDynamicsDialog
class | BALL::VIEW::MolecularFileDialog
class | BALL::VIEW::NetworkPreferences
class | BALL::VIEW::ParsedFunctionDialog
class | BALL::VIEW::PeptideDialog
class | BALL::VIEW::Preferences
class | BALL::VIEW::PythonSettings
class | BALL::VIEW::ServerPreferences
class | BALL::VIEW::SetCamera
class | BALL::VIEW::SetClippingPlane
class | BALL::VIEW::ShortcutDialog
class | BALL::VIEW::SnapshotVisualisationDialog
class | BALL::VIEW::StageSettings
class | BALL::VIEW::StereoSettingsDialog
class | BALL::VIEW::UndoManagerDialog
class | BALL::VIEW::ColorTable
class | BALL::VIEW::HotkeyTable

## Detailed Description

This section contains all dialogs, which are created with QT. All dialogs should be constructed with the QT designer and the implementation has to be sourced out to a derived class. (This sound worse, than it is. Just have a look at a simple dialog (e.g. SetCamera ) and you will see its not that bad.) This outsourcing has two goals:

- Seperate the design of the dialogs from the implementation. This accelerates the redesign of existing dialogs.
- Make the dialogs independent from a specific version of the QT libary (Otherwise there are serious problems, because QT is inconsistent between different versions of the libary.)

Some dialogs are derived from ModularWidget to participate in the sending and receiving of Message 's. The other dialogs have to be informed manualy, it something happend, that they need to know, e.g. to disable certain controls.