ObjCryst::WXDiffractionSingleCrystal Class Reference

WX Class for DiffractionDataSingleCrystal objects. More...

Inheritance diagram for ObjCryst::WXDiffractionSingleCrystal:

[legend]Collaboration diagram for ObjCryst::WXDiffractionSingleCrystal:

[legend]List of all members.


Public Member Functions
	WXDiffractionSingleCrystal (wxWindow parent, DiffractionDataSingleCrystal )
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 Member Functions
void	OnMenuSimulate (wxCommandEvent &WXUNUSED(event))
void	OnMenuImport (wxCommandEvent &event)
void	OnMenuSaveHKLIobsIcalc (wxCommandEvent &WXUNUSED(event))
void	OnMenuSaveHKLFcalc (wxCommandEvent &WXUNUSED(event))
void	OnMenuSetWavelength (wxCommandEvent &event)
void	OnChangeCrystal (wxCommandEvent &WXUNUSED(event))
Private Attributes
WXFieldChoice *	mpFieldCrystal
DiffractionDataSingleCrystal *	mpData
REAL	mChi2
REAL	mGoF
REAL	mRwp
REAL	mRp

Detailed Description

WX Class for DiffractionDataSingleCrystal objects.

Constructor & Destructor Documentation

ObjCryst::WXDiffractionSingleCrystal::WXDiffractionSingleCrystal ( wxWindow * parent,

DiffractionDataSingleCrystal *

)

Member Function Documentation

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

Reimplemented from ObjCryst::WXRefinableObj.

void ObjCryst::WXDiffractionSingleCrystal::OnChangeCrystal ( wxCommandEvent & WXUNUSED(event) ) [private]

void ObjCryst::WXDiffractionSingleCrystal::OnMenuImport ( wxCommandEvent & event ) [private]

void ObjCryst::WXDiffractionSingleCrystal::OnMenuSaveHKLFcalc ( wxCommandEvent & WXUNUSED(event) ) [private]

void ObjCryst::WXDiffractionSingleCrystal::OnMenuSaveHKLIobsIcalc ( wxCommandEvent & WXUNUSED(event) ) [private]

void ObjCryst::WXDiffractionSingleCrystal::OnMenuSetWavelength ( wxCommandEvent & event ) [private]

void ObjCryst::WXDiffractionSingleCrystal::OnMenuSimulate ( wxCommandEvent & WXUNUSED(event) ) [private]

virtual void ObjCryst::WXDiffractionSingleCrystal::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.
Reimplemented from ObjCryst::WXRefinableObj.