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
In current implementation render state notation parser extracts state descriptions only, which requires extra effort from the application. It also introduces a lot of additional structs that largely duplicate core structs with only difference that instead of object pointers they use object names (e.g. pVS vs pVSName).
To make the render state notion API more convenient to use it is proposed to change the API as follows:
Add pDevice member to RenderStateNotationParserCreateInfo
This could be a serialization device or any actual rendering device
Add DeviceBits member that will only be used for archiver
Replace all current methods Get*ByName and Get*ByIndex with Create and Create*ByIndex
To make object creation more flexible, add callbacks to override the state:
This should make the parser API much more concise and convenient to use - API objects can be created directly, while required states can be easily overriden
The text was updated successfully, but these errors were encountered:
In current implementation render state notation parser extracts state descriptions only, which requires extra effort from the application. It also introduces a lot of additional structs that largely duplicate core structs with only difference that instead of object pointers they use object names (e.g. pVS vs pVSName).
To make the render state notion API more convenient to use it is proposed to change the API as follows:
DeviceBits
member that will only be used for archiverGet*ByName
andGet*ByIndex
withCreate
andCreate*ByIndex
Similar for other object types.
This should make the parser API much more concise and convenient to use - API objects can be created directly, while required states can be easily overriden
The text was updated successfully, but these errors were encountered: