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
Currently device activation/deactivation is handled by topology. This seems rather counter intuitive, as of_core is the NApp which generates the events which create the devices, and creates the events which then modify the activation state. This seems like an unnecessary level of indirection to have topology manage the activation/deactivation, when of_core already has already acquired the device for creating the event.
The text was updated successfully, but these errors were encountered:
Currently device activation/deactivation is handled by
topology
. This seems rather counter intuitive, asof_core
is the NApp which generates the events which create the devices, and creates the events which then modify the activation state. This seems like an unnecessary level of indirection to havetopology
manage the activation/deactivation, whenof_core
already has already acquired the device for creating the event.The text was updated successfully, but these errors were encountered: