osvr::client::ClientInterfaceObjectManager Class Reference

Class hiding the details of the interaction of the path tree and interface objects/osvr::client::InterfaceTree. More...

#include <osvr/Client/ClientInterfaceObjectManager.h>

Public Member Functions
	ClientInterfaceObjectManager (common::PathTreeOwner &tree, RemoteHandlerFactory &handlerFactory, common::ClientContext &ctx)
ClientInterfaceObjectManager &	operator= (ClientInterfaceObjectManager const &)=delete
void	addInterface (common::ClientInterfacePtr const &iface, bool verboseFailure=true)
void	releaseInterface (common::ClientInterfacePtr const &iface)
void	updateHandlers ()
	run update on all remote handlers

Detailed Description

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.

Definition at line 59 of file ClientInterfaceObjectManager.h.

Member Function Documentation

void osvr::client::ClientInterfaceObjectManager::addInterface	(	common::ClientInterfacePtr const &	iface,
		bool	verboseFailure = true
	)

Parameters

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.

Definition at line 57 of file ClientInterfaceObjectManager.cpp.

---

The documentation for this class was generated from the following files:

• osvr/Client/ClientInterfaceObjectManager.h
• src/osvr/Client/ClientInterfaceObjectManager.cpp