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
For Beta 2, a major goal is to have classes to serve as interfaces for getting/setting data on Wwise objects. The core architecture for that is already available in objects.py. The idea is that WwiseObjectInfo will offer some sort of a factory function or conversion function that returns an instance of a WwiseObject subclass, which can be any type listed in the Wwise Objects Reference.
Motivation
This is to facilitate getting and setting data on Wwise objects. At the moment, that requires function calls (e.g. ak.wwise.core.object.set) with property/reference names and values as arguments, which is a hassle. More specifically, the pain points to address with this feature are:
Lack of autocompletion.
Lack of constraints (e.g. enumerated values).
Lack of type-hints or any form of type-check.
The text was updated successfully, but these errors were encountered:
Summary
For Beta 2, a major goal is to have classes to serve as interfaces for getting/setting data on Wwise objects. The core architecture for that is already available in
objects.py
. The idea is thatWwiseObjectInfo
will offer some sort of a factory function or conversion function that returns an instance of aWwiseObject
subclass, which can be any type listed in the Wwise Objects Reference.Motivation
This is to facilitate getting and setting data on Wwise objects. At the moment, that requires function calls (e.g.
ak.wwise.core.object.set
) with property/reference names and values as arguments, which is a hassle. More specifically, the pain points to address with this feature are:The text was updated successfully, but these errors were encountered: