Caelum::AccesorPropertyDescriptor< TargetT, ParamT, InParamT, OutParamT > Class Template Reference

ValuePropertyDescriptor implementation based on function pointers to get/set methods. More...

#include <TypeDescriptor.h>

Inheritance diagram for Caelum::AccesorPropertyDescriptor< TargetT, ParamT, InParamT, OutParamT >:

Public Types
typedef void(TargetT::*	SetFunc) (InParamT)
typedef OutParamT(TargetT::*	GetFunc) (void) const

Public Member Functions
	AccesorPropertyDescriptor (GetFunc getFunc, SetFunc setFunc)
virtual bool	canGetValue () const
	If the value of the property can be read (true means write-only). More...
virtual bool	canSetValue () const
	If the value of the property can be set (false means read-only).
virtual const ParamT	getValueTyped (const void *target) const
	Get the property's value.
virtual void	setValueTyped (void *target, const ParamT &value) const
	Set the property's value.

Detailed Description

template<class TargetT, typename ParamT, typename InParamT = const ParamT&, typename OutParamT = const ParamT>
class Caelum::AccesorPropertyDescriptor< TargetT, ParamT, InParamT, OutParamT >

ValuePropertyDescriptor implementation based on function pointers to get/set methods.

Member Function Documentation

template<class TargetT , typename ParamT , typename InParamT = const ParamT&, typename OutParamT = const ParamT>

virtual bool Caelum::AccesorPropertyDescriptor< TargetT, ParamT, InParamT, OutParamT >::canGetValue ( ) const

inlinevirtual

If the value of the property can be read (true means write-only).

This is false for write-only properties. Write-only properties are generally a bad idea but they are supported. Scripting (with .os files) doesn't actually require reading existing values.

Implements Caelum::ValuePropertyDescriptor.

---

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

• /home/pavel/workspace/ogre-caelum/main/include/TypeDescriptor.h