This can be done with a lot less overhead by using one of the object's properties to store the activation flag, so that all the nearly redundant trigger methods can be folded into one. |
||
|---|---|---|
| .. | ||
| static | ||
| CMakeLists.txt | ||
This can be done with a lot less overhead by using one of the object's properties to store the activation flag, so that all the nearly redundant trigger methods can be folded into one. |
||
|---|---|---|
| .. | ||
| static | ||
| CMakeLists.txt | ||