#include <HPropert.h>
Inheritance diagram for HPropertyInfo:
Classes under HPropertyInfo are used to supply a UI context for corresponding HProperty classes to be set and manipulated by the user in the PWS. Since the UI context is the same for each instance which uses the same property, the HPropertyInfo derived classes should be declared inside the application class. In other words inside the InitInstance of the CWinApp derived class.
Definition at line 23 of file HPropert.h.
|
Controls when the property will be displayed in the PWS for the user to enter values. From the SDK point of view, a plugin possess a list of properties which are all grouped together inside a property panel. The panel is displayable by clicking on the little expand triangle that is visible on a node of the PWS tree. A plugin property pannel may be accessible from different context. For example, the properties for a turbulence plugin may be accessible from a material node, from a material shortcut on a model or on a group and from a material shortcut on a model shortcut in choreography. For some particular properties, it may be desirable to let the user modify them only when inside a material node for instance.
Definition at line 26 of file HPropert.h. |
|
Controls how a plugin can switch visibility of a property in the PWS for the user to enter values. This is different than DrawWhen in that VisibleWhen imposes restriction on the actions of HProperty::Show during plugin execution.
Definition at line 27 of file HPropert.h. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Only shows up if user has Show Advanced Proerties on |
|
The property does not animate over time |
|
|
|
|
|
Both cache and instanes are read only |
|
Cache is read only meaning that the user will not be able to change the values of the cache's property. The user may be able to change the values of the instance's property though.
|
|
Instance is read only meaning that the user will not be able to change the values of the instance's property. The user may be able to change the values of the cache's property though.
|
|
|
|
Creates a new HPropertyInfo or any of its derived class UI slot in a property panel in the PWS.
Reimplemented in HBoolPropertyInfo, HAttrPropertyInfo, HFloatPropertyInfo, HPercentPropertyInfo, HIntPropertyInfo, HRotatePropertyInfo, HButtonPropertyInfo, HBiasPropertyInfo, HStringPropertyInfo, HFilenamePropertyInfo, HDirPropertyInfo, HTimePropertyInfo, HTimeRangePropertyInfo, HTransformPropertyInfo, HVectorPropertyInfo, HVectorPropertyNoSubsInfo, HVector2PropertyInfo, HColorPropertyInfo, HScalePropertyInfo, HTranslatePropertyInfo, HPointerPropertyInfo, HClipPropertyInfo, HGradientPropertyInfo, and HDataPropertyInfo. |
|
Definition at line 30 of file HPropert.h. |
|
Will only show up if user has Show Advanced Proerties on |
|
|
|
Constant will not animate over time |
|
|
|
|
|
|
|
Localized names are the names of properties that appears in the left column of the property panel in the PWS. This name should be retrieved from a string resource to allow easy localization (ie: translation). For example: string.LoadString(IDS_BUMPSTRENGTH); m_bumpinfo = HFloatPropertyInfo::SetLocalizedName( string, String("Bump Strength") ); |
|
For backward comp with V9.0o and older.
|
|
Match names are labels used to identify the property when the property value is stored in an A:M file (project, model, meterial, etc. files). Any HProperty derived class associated to a corresponding HPropertyInfo derived class will automatically have its properties values stored in the appropriate A:M file. Match names should not be localized. DLLPlugins derived classes also have the possibility to store and retrieve data other than properties with the Save and ParseArg functions.
|
|
For backward comp with V9.0o and older.
|
|
Use this to have HxtOnPtrMessage called for your property. This is a speed hit (it is slow) so only set it if you really want the function to be called. |
|
Both cache and instanes will be read only meaning the user will not be able to change the values of the property |
|
User will not be able to change the value on the cache, SetReadOnly should be set to FALSE if you want the instances to be able to be editied |
|
User will not be able to change the value on the instance, SetReadOnly should be set to FALSE if you want the caches to be able to be editied |
|
|
|
|
Generated on Thu Oct 27 11:46:57 2005 with
1.4.5 written by Dimitri van Heesch,
© 1997-2001