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
The standard way to define transitions and monitored properties is to hardcode their specification in a device sub-class in init. This is fine if all transitions and properties are known in advance, but creates a hurdle when creating devices dynamically at run time. See https://groups.google.com/forum/#!topic/zetta-discuss/XPVzd0gLnSE for discussion.
Instead of passing the 'config' object to the sub-class, propose the addition of methods which allow appending entries before init() finishes. Something like:
The standard way to define transitions and monitored properties is to hardcode their specification in a device sub-class in init. This is fine if all transitions and properties are known in advance, but creates a hurdle when creating devices dynamically at run time. See https://groups.google.com/forum/#!topic/zetta-discuss/XPVzd0gLnSE for discussion.
Instead of passing the 'config' object to the sub-class, propose the addition of methods which allow appending entries before init() finishes. Something like:
The text was updated successfully, but these errors were encountered: