You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/properties.md
+17-13Lines changed: 17 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,5 @@
1
+
\defgroup module_properties Properties
2
+
@{
1
3
2
4
# Properties
3
5
@@ -22,10 +24,10 @@ The following types are available for properties
22
24
* bool
23
25
* int8
24
26
* int16
25
-
*int
27
+
*int32
26
28
* uint8
27
29
* uint16
28
-
*uint
30
+
*uint32
29
31
* float
30
32
* double
31
33
* string
@@ -59,7 +61,7 @@ For the framework, two types of property classes exist.
59
61
60
62
For each of the above types, besides _normal_ property types that are visible and stored as is, there are three different attributes available:
61
63
62
-
* Hidden - ```flxPropertyHidden<type>```, ```flxPropertyRWHidden<type>``` - The property isn't presented in menu systems, but can be used by an object to store/persist it's value.
64
+
* Hidden - ```flxPropertyHidden<type>```, ```flxPropertyRWHidden<type>``` - The property isn't presented in menu systems, but can be used by an object to store/persist it's value.
63
65
* Secure - ```flxPropertySecure<type>```, ```flxPropertyRWSecure<type>``` -The value of the property is encrypted before saving the value. This value is only written internally (not to a public JSON file)
64
66
* Secret - ```flxPropertySecret<type>```, ```flxPropertyRWSecret<type>``` - The value is _hidden_ and _secure_.
65
67
@@ -85,10 +87,10 @@ Available Property Types:
85
87
* flxPropertyBool
86
88
* flxPropertyInt8
87
89
* flxPropertyInt16
88
-
* flxPropertyInt
89
-
* flxPropertyUint8
90
-
* flxPropertyUint16
91
-
* flxPropertyUint
90
+
* flxPropertyInt32
91
+
* flxPropertyUInt8
92
+
* flxPropertyUInt16
93
+
* flxPropertyUInt32
92
94
* flxPropertyFloat
93
95
* flxPropertyDouble
94
96
* flxPropertyString
@@ -176,10 +178,10 @@ Where:
176
178
* flxPropertyRWBool - bool property
177
179
* flxPropertyRWInt8 - integer 8 property
178
180
* flxPropertyRWInt16 - integer 16 property
179
-
*flxPropertyRWInt - integer property
180
-
*flxPropertyRWUint8 - unsigned 8 integer
181
-
*flxPropertyRWUint16 - unsigned 16 integer
182
-
*flxPropertyRWUint - unsigned integer
181
+
*flxPropertyRWInt32 - integer 32 property
182
+
*flxPropertyRWUInt8 - unsigned 8 integer
183
+
*flxPropertyRWUInt16 - unsigned 16 integer
184
+
*flxPropertyRWUInt32 - unsigned 32 integer
183
185
* flxPropertyRWFloat - float
184
186
* flxPropertyRWDouble - double
185
187
* flxPropertyRWString - string -> std::string
@@ -274,7 +276,7 @@ Note: If an initial value was set for the property, the value is passed to the _
274
276
275
277
Data limits define restrictions on the values the input parameter accepts. There are two types of data limits: range and valid value sets.
276
278
277
-
*Data Range*
279
+
_Data Range_
278
280
This represents the minimum and maximum values a input parameter will accept. The values can be specified at property definition (the preferred method) and also set at runtime.
279
281
280
282
To set the range at parameter definition, just set the declared parameter to the range using a C++ initializer list ```{ min, max}```
@@ -311,7 +313,7 @@ For Example:
311
313
312
314
This changes the data range accepted by the object and deletes any existing data limit.
313
315
314
-
*Data Valid Value Set*
316
+
_Data Valid Value Set_
315
317
316
318
This represents data limit provides a defined set of valid values for the property. The limit is defined by a set of _name, value_ pairs that enable a human readable presentation for the values a property will accept. The values can be specified at property definition and also set at runtime.
317
319
@@ -367,3 +369,5 @@ Or for an entire parameter list:
367
369
```
368
370
369
371
The values are added to the current valid value list. If a _ValidValue_ data limit was not in place when called, any current limit (i.e. range limit) is deleted and a valid value limit is put in place.
0 commit comments