|
6 | 6 | * data with the Settings interface, when the data types
|
7 | 7 | * are not supported by the Setting annotation.
|
8 | 8 | *
|
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. |
18 | 15 | *
|
19 | 16 | * These examples are not intended to be the bible for
|
20 | 17 | * achieving these effects, but instead a set of ideas and
|
|
30 | 27 | */
|
31 | 28 |
|
32 | 29 | /* Our goal for each vec3 is to approximate the following
|
33 |
| - * (invalid) code: |
| 30 | + * code: |
34 | 31 | *
|
35 | 32 | * [Setting]
|
36 | 33 | * vec3 Data;
|
37 | 34 | *
|
| 35 | + * Remember, the above code is valid, but this file will |
| 36 | + * show techniques that are applicable to unsupported data |
| 37 | + * types. |
| 38 | + * |
38 | 39 | * Each example has:
|
39 | 40 | * - a declaration, which defines the objects that we want
|
40 | 41 | * to store.
|
|
0 commit comments