ObjCryst::WXTexturePhaseMarchDollase Class Reference

Class to display one Preferred Orientation phase using the March-Dollase parametrization. More...

Inheritance diagram for ObjCryst::WXTexturePhaseMarchDollase:

[legend]Collaboration diagram for ObjCryst::WXTexturePhaseMarchDollase:

[legend]List of all members.

Public Member Functions
	WXTexturePhaseMarchDollase (wxWindow *parent, TexturePhaseMarchDollase *, TextureMarchDollase *)
	~WXTexturePhaseMarchDollase ()
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.
Private Attributes
wxBoxSizer *	mpSizer
WXCrystObjBasicList	mList
TexturePhaseMarchDollase *	mpTexturePhaseMarchDollase

---

Detailed Description

Class to display one Preferred Orientation phase using the March-Dollase parametrization.

---

Constructor & Destructor Documentation

ObjCryst::WXTexturePhaseMarchDollase::WXTexturePhaseMarchDollase (  wxWindow *  parent, TexturePhaseMarchDollase *  , TextureMarchDollase *  )

ObjCryst::WXTexturePhaseMarchDollase::~WXTexturePhaseMarchDollase (   )

---

Member Function Documentation

virtual void ObjCryst::WXTexturePhaseMarchDollase::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.

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

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

TexturePhaseMarchDollase* ObjCryst::WXTexturePhaseMarchDollase::mpTexturePhaseMarchDollase [private]

---

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

• wxPowderPattern.h

---