Skip to content

Commit 27ecb3e

Browse files
authored
Update SettingsAdvancedTest
Update wording now that vec3 Settings are natively supported.
1 parent 010e1ad commit 27ecb3e

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

Diff for: Plugin_SettingsAdvancedTest.as

+11-10
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,12 @@
66
* data with the Settings interface, when the data types
77
* are not supported by the Setting annotation.
88
*
9-
* In this demonstration, we will be storing vec3 objects,
10-
* since they are not supported by the Setting annotation
11-
* directly, but they are still simple enough to be a
12-
* good example.
13-
*
14-
* One shortcoming of this example is that it is rather
15-
* cheap and easy to construct vec3 objects on the fly,
16-
* where needed. These techniques are most useful when
17-
* applied to objects that are more expensive to construct.
9+
* In this demonstration, we will be storing vec3 objects.
10+
* This data type is supported by the Settings interface,
11+
* natively, but they will serve as a simple example that
12+
* can be extended to more complex use cases, and in fact,
13+
* these techniques are most useful when applied to objects
14+
* that are more expensive to construct.
1815
*
1916
* These examples are not intended to be the bible for
2017
* achieving these effects, but instead a set of ideas and
@@ -30,11 +27,15 @@
3027
*/
3128

3229
/* Our goal for each vec3 is to approximate the following
33-
* (invalid) code:
30+
* code:
3431
*
3532
* [Setting]
3633
* vec3 Data;
3734
*
35+
* Remember, the above code is valid, but this file will
36+
* show techniques that are applicable to unsupported data
37+
* types.
38+
*
3839
* Each example has:
3940
* - a declaration, which defines the objects that we want
4041
* to store.

0 commit comments

Comments
 (0)