Main Page | Namespace List | Class Hierarchy | Alphabetical List | Class List | File List | Namespace Members | Class Members | File Members | Related Pages

ObjCryst::WXZAtom Class Reference

Inheritance diagram for ObjCryst::WXZAtom:

Inheritance graph
[legend]
Collaboration diagram for ObjCryst::WXZAtom:

Collaboration graph
[legend]
List of all members.

Public Member Functions

 WXZAtom (wxWindow *parent, ZAtom *)
virtual void CrystUpdate (const bool updateUI=false, const bool mutexlock=false)
 Get new values to be displayed from the underlying object, and raise flag if an UI update is necessary.

virtual void UpdateUI (const bool mutexlock=false)
 Update the User Interface, if necessary.

void OnChangeScattPow (wxCommandEvent &WXUNUSED(event))

Private Attributes

ZAtommpZAtom
wxBoxSizer * mpSizer
WXCrystObjBasicList mList
WXFieldStringmpFieldName
WXFieldChoicempFieldScattPower

Constructor & Destructor Documentation

ObjCryst::WXZAtom::WXZAtom wxWindow *  parent,
ZAtom
 


Member Function Documentation

virtual void ObjCryst::WXZAtom::CrystUpdate const bool  updateUI = false,
const bool  mutexlock = false
[virtual]
 

Get new values to be displayed from the underlying object, and raise flag if an UI update is necessary.

The actual GUI update is not made here. UpdateUI() should be called separately, from the main thread.

Parameters:
updateUI: if true, this will call UpdateUI, either directly (if in the main thread), or by sending a message.
mutexlock: if true, a Mutex will be used to lock the data shared between main and background thread. The idea is to only use a few Mutexes to lock data from the top objects (wxRefinableObj,...), when calling CrystUpdate() and UpdateUI(). As sub-objects (WXField,...) are only updated from within a top object, the mutex lock in the top object will also lock the data in the sub-objects.

Implements ObjCryst::WXCrystObjBasic.

void ObjCryst::WXZAtom::OnChangeScattPow wxCommandEvent &  WXUNUSED(event)  ) 
 

virtual void ObjCryst::WXZAtom::UpdateUI const bool  mutexlock = false  )  [virtual]
 

Update the User Interface, if necessary.

Parameters:
mutexlock: if true, a Mutex will be used to lock the data shared between main and background thread.
The idea is to only use a few Mutexes to lock data from the top objects (wxRefinableObj,...), when calling CrystUpdate() and UpdateUI(). As sub-objects (WXField,...) are only updated from within a top object, the mutex lock in the top object will also lock the data in the sub-objects.

Implements ObjCryst::WXCrystObjBasic.


Member Data Documentation

WXCrystObjBasicList ObjCryst::WXZAtom::mList [private]
 

WXFieldString* ObjCryst::WXZAtom::mpFieldName [private]
 

WXFieldChoice* ObjCryst::WXZAtom::mpFieldScattPower [private]
 

wxBoxSizer* ObjCryst::WXZAtom::mpSizer [private]
 

ZAtom* ObjCryst::WXZAtom::mpZAtom [private]
 


The documentation for this class was generated from the following file:
Generated on Tue Nov 14 15:08:18 2006 for ObjCryst++ by doxygen 1.3.6