ObjCryst::WXMolAtom Class Reference

wx class for MolAtom objects More...

Inheritance diagram for ObjCryst::WXMolAtom:

[legend]Collaboration diagram for ObjCryst::WXMolAtom:

[legend]List of all members.

Public Member Functions
	WXMolAtom (wxWindow *parent, MolAtom *)
virtual	~WXMolAtom ()
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 &)
Private Attributes
MolAtom *	mpMolAtom
wxBoxSizer *	mpSizer
WXCrystObjBasicList	mList
WXFieldString *	mpFieldName
WXFieldChoice *	mpFieldScattPower

---

Detailed Description

wx class for MolAtom objects

---

Constructor & Destructor Documentation

ObjCryst::WXMolAtom::WXMolAtom (  wxWindow *  parent, MolAtom *  )

virtual ObjCryst::WXMolAtom::~WXMolAtom (   )  [virtual]

---

Member Function Documentation

virtual void ObjCryst::WXMolAtom::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::WXMolAtom::OnChangeScattPow (  wxCommandEvent &   )

virtual void ObjCryst::WXMolAtom::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::WXMolAtom::mList [private]

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

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

MolAtom* ObjCryst::WXMolAtom::mpMolAtom [private]

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

---

The documentation for this class was generated from the following file:

• wxMolecule.h

---