Spent some more time on my property grid attempt. Finally got it working, had to give my reflection system some love. The nested types/arrays are pretty ugly but I have no ideas how to improve so I'm moving on...pic.twitter.com/Wc8fWc6EAy
-
I suppose I am conflating reflection and serialization. I automate serialization through reflection, but in order to do that array types must also reflect certain members. Pushback, clear, data, size, reserve. Maybe one more I’m forgetting.
And I’m not using libclang, as you are. I have in the past and I found that because it introduces a pre-build step in order to get compile-time reflection, I’ve preferred just using constexpr and a few helper macros.
-
-
The libclang has benefits like being able to get exact enum values, even ones that include macros and expressions. It can also give me info on things like "abstractness", underlying types, etc... It is rather slow but it gives me what I need without crazy macro magic.
-
It also allows me to export that reflection data via a sqlite DB for external tools to use. Idea being is that some degree of that data could be used by DCC plugins to move certain authoring operations out of the engine. i.e. physics filter enums, mesh flags, etc...
Keskustelun loppu
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.