OSVR-Core
|
Class hiding the details of the interaction of the path tree and interface objects/osvr::client::InterfaceTree. More...
#include <ClientInterfaceObjectManager.h>
Public Member Functions | |
OSVR_CLIENT_EXPORT | ClientInterfaceObjectManager (common::PathTreeOwner &tree, RemoteHandlerFactory &handlerFactory, common::ClientContext &ctx) |
ClientInterfaceObjectManager & | operator= (ClientInterfaceObjectManager const &)=delete |
OSVR_CLIENT_EXPORT void | addInterface (common::ClientInterfacePtr const &iface, bool verboseFailure=true) |
OSVR_CLIENT_EXPORT void | releaseInterface (common::ClientInterfacePtr const &iface) |
OSVR_CLIENT_EXPORT void | updateHandlers () |
run update on all remote handlers | |
Class hiding the details of the interaction of the path tree and interface objects/osvr::client::InterfaceTree.
Designed to pull out a chunk of functionality from individual ClientContext implementations for sharing.
I tend to hate classes named "...Manager", but it seemed like the most suitable name at the time. Refactor to rename is welcome.
void osvr::client::ClientInterfaceObjectManager::addInterface | ( | common::ClientInterfacePtr const & | iface, |
bool | verboseFailure = true |
||
) |
verboseFailure | Whether we should allow verbose printing of messages in case this interface doesn't immediately resolve to a source. For instance, you'd want this to be "false" when setting up an analysis plugin context ahead of its autodetected sources. |