API for allowing Contexts to register across the Context border. More...

Inheritance diagram for strange.extensions.context.api.ICrossContextCapable:

Public Member Functions
void	AssignCrossContext (ICrossContextCapable childContext)
	Add cross-context functionality to a child context being added.

void	RemoveCrossContext (ICrossContextCapable childContext)
	Clean up cross-context functionality from a child context being removed.

object	GetComponent< T > ()
	Request a component from the context (might be useful in certain cross-context situations) This is technically a deprecated methodology. More...

object	GetComponent< T > (object name)
	Request a component from the context (might be useful in certain cross-context situations) This is technically a deprecated methodology. More...

Properties
ICrossContextInjectionBinder	injectionBinder `[get, set]`
	All cross-context capable contexts must implement an injectionBinder.

IDispatcher	crossContextDispatcher `[get, set]`
	Set and get the shared system bus for communicating across contexts.

Detailed Description

API for allowing Contexts to register across the Context border.

Implement this interface to create a binding context that can communicate across Context boundaries.

MVCSContext inherits CrossContext to obtain important capabilities, such as shared injections.

Member Function Documentation

object strange.extensions.context.api.ICrossContextCapable.GetComponent< T > ( )

Request a component from the context (might be useful in certain cross-context situations) This is technically a deprecated methodology.

Bind using CrossContext() instead.

object strange.extensions.context.api.ICrossContextCapable.GetComponent< T > ( object name)

Request a component from the context (might be useful in certain cross-context situations) This is technically a deprecated methodology.

Bind using CrossContext() instead.

The documentation for this interface was generated from the following file: