Phidget Manager - Revision history

Burley at 16:41, 24 March 2022

2022-03-24T16:41:16Z

← Older revision		Revision as of 16:41, 24 March 2022
Line 12:		Line 12:
	The primary function of a Phidget Manager is to fire an attach event for each new device channel when a Phidget becomes available to a system, and to fire a detach event for each device channel that is no longer available when the Phidget is removed from the system. For example, when a 1044_0 - PhidgetSpatial is connected, a Phidget Manager would fire three attach events, one for each device channel, as illustrated below:		The primary function of a Phidget Manager is to fire an attach event for each new device channel when a Phidget becomes available to a system, and to fire a detach event for each device channel that is no longer available when the Phidget is removed from the system. For example, when a 1044_0 - PhidgetSpatial is connected, a Phidget Manager would fire three attach events, one for each device channel, as illustrated below:

	[[Image:manager22.jpg\|link=\|~~1000px~~\|alt=]]		[[Image:manager22.jpg\|link=\|850px\|alt=]]

	==Using the Phidget Manager==		==Using the Phidget Manager==

Jdecoux at 20:40, 28 February 2019

2019-02-28T20:40:37Z

← Older revision		Revision as of 20:40, 28 February 2019
Line 60:		Line 60:
	</div>		</div>

	A further example would be "HelloWorld" for most [[~~Software Overview#Language Support~~\|supported languages]] uses the Phidget Manager.		A further example would be "HelloWorld" for most [[Programming_Resources\|supported languages]] uses the Phidget Manager.

	==Opening a Manager Channel==		==Opening a Manager Channel==

Chad: /* Opening a Manager Channel */

2017-07-13T22:12:27Z

Opening a Manager Channel

← Older revision		Revision as of 22:12, 13 July 2017
Line 66:		Line 66:
	A manager channel passed to a Phidget Manager attach handler is assigned all of the matching parameters for the Phidget device and the device channel the manager channel refers to; however, the manager channel is not attached to the device channel, and is not receiving data and status information from the device.		A manager channel passed to a Phidget Manager attach handler is assigned all of the matching parameters for the Phidget device and the device channel the manager channel refers to; however, the manager channel is not attached to the device channel, and is not receiving data and status information from the device.

	User code may {{Code\|Open()}} a manager channel, and just like a channel created by the user code, the Phidget library will begin trying to match the manager channel with a device channel. User code may also set attach and detach handlers on the manager channel, and set change event handlers. The manager channel can be treated exactly the same as a user channel~~, except that the manager channel must never be deleted, and after calling {{Code\|Close()}}, should not be referred to again~~.		User code may {{Code\|Open()}} a manager channel, and just like a channel created by the user code, the Phidget library will begin trying to match the manager channel with a device channel. User code may also set attach and detach handlers on the manager channel, and set change event handlers. The manager channel can be treated exactly the same as a user channel.

Chad: /* General Overview */

2017-07-13T17:18:41Z

General Overview

← Older revision		Revision as of 17:18, 13 July 2017
Line 2:		Line 2:
	==General Overview==		==General Overview==

	The Phidget Manager is an interface into the device channels available to the Phidget library. The API is strictly asynchronous, a continuously monitors channels as they attach and detach. Each Phidget exports one or more device channels, and when a Phidget is plugged into a system (or become available over the network), an attach event is fired for each channel available on that Phidget.		The Phidget Manager is an interface into the device channels available to the Phidget library. The API is strictly asynchronous, and continuously monitors channels as they attach and detach.

	It is important to understand the concepts of '''attach''' and '''detach''' as the they relate to the manager. A manager attach does not imply that a user channel has attached to a device channel, but that the device channel ~~have become available. The~~ device channel is now ready to be attached to a user channel. When a user channel closes and detaches from a device channel a manager event ~~will~~ not be fired. A manager '''detach''' event is fired when the Phidget ~~device~~ is removed from the system.		Each Phidget exports one or more device channels, and when a Phidget is plugged into a system (or becomes available over the network), a manager attach event is fired for each channel available from the Phidget. When the Phidget is removed from the system, a manger detach event is fired for each channel that is no longer available.

			It is important to understand the concepts of '''attach''' and '''detach''' as the they relate to the manager. A manager attach does not imply that a user channel has attached to a device channel, but that the device channel has ''appeared'', and the device channel is now ready to be attached to a user channel. When a user channel closes and detaches from a device channel, a manager event is not fired. A manager '''detach''' event is fired when the Phidget is removed from the system.

	==Purpose==		==Purpose==

Chad: /* Using the Phidget Manager */

2017-07-13T17:15:29Z

Using the Phidget Manager

← Older revision		Revision as of 17:15, 13 July 2017
Line 26:		Line 26:

	static void CCONV		static void CCONV
	mgrAttachHandler(PhidgetManagerHandle mgr, void *ctx, PhidgetHandle ~~devch~~) {		mgrAttachHandler(PhidgetManagerHandle mgr, void *ctx, PhidgetHandle mgrch) {

	PhidgetLog_log("%P attached", ~~devch~~);		PhidgetLog_log("%P attached", mgrch);
	}		}

	static void CCONV		static void CCONV
	mgrDetachHandler(PhidgetManagerHandle mgr, void *ctx, PhidgetHandle ~~devch~~) {		mgrDetachHandler(PhidgetManagerHandle mgr, void *ctx, PhidgetHandle mgrch) {

	PhidgetLog_log("%P detached", ~~devch~~);		PhidgetLog_log("%P detached", mgrch);
	}		}

Chad: /* Opening a Manager Channel= */

2017-07-13T17:13:32Z

Opening a Manager Channel=

← Older revision		Revision as of 17:13, 13 July 2017
Line 60:		Line 60:
	A further example would be "HelloWorld" for most [[Software Overview#Language Support\|supported languages]] uses the Phidget Manager.		A further example would be "HelloWorld" for most [[Software Overview#Language Support\|supported languages]] uses the Phidget Manager.

	==Opening a Manager Channel===		==Opening a Manager Channel==

			A manager channel passed to a Phidget Manager attach handler is assigned all of the matching parameters for the Phidget device and the device channel the manager channel refers to; however, the manager channel is not attached to the device channel, and is not receiving data and status information from the device.

			User code may {{Code\|Open()}} a manager channel, and just like a channel created by the user code, the Phidget library will begin trying to match the manager channel with a device channel. User code may also set attach and detach handlers on the manager channel, and set change event handlers. The manager channel can be treated exactly the same as a user channel, except that the manager channel must never be deleted, and after calling {{Code\|Close()}}, should not be referred to again.

Chad at 17:04, 13 July 2017

2017-07-13T17:04:43Z

← Older revision		Revision as of 17:04, 13 July 2017
Line 59:		Line 59:

	A further example would be "HelloWorld" for most [[Software Overview#Language Support\|supported languages]] uses the Phidget Manager.		A further example would be "HelloWorld" for most [[Software Overview#Language Support\|supported languages]] uses the Phidget Manager.

			==Opening a Manager Channel===

Chad: /* Using the Phidget Manager */

2017-07-13T17:04:00Z

Using the Phidget Manager

Show changes

Chad: /* Purpose */

2017-07-13T16:42:03Z

Purpose

← Older revision		Revision as of 16:42, 13 July 2017
Line 8:		Line 8:
	==Purpose==		==Purpose==

	The ~~main~~ function of ~~the~~ Phidget Manager is to ~~launch events~~ when a Phidget ~~attaches or detaches~~, ~~so you can execute code to prepare those Phidgets for use. For Phidgets that have multiple objects~~ and~~/or channels (which happens~~ to ~~be most of them),~~ a ~~separate attach and~~ detach event ~~will trigger~~ for each ~~one~~. For example, when ~~the~~ 1044_0 - PhidgetSpatial is connected, ~~the~~ Phidget Manager would ~~launch~~ three attach events, one for each ~~distinct object~~, as illustrated below:		The primary function of a Phidget Manager is to fire an attach event for each new device channel when a Phidget becomes available to a system, and to fire a detach event for each device channel that is no longer available when the Phidget is removed from the system. For example, when a 1044_0 - PhidgetSpatial is connected, a Phidget Manager would fire three attach events, one for each device channel, as illustrated below:

	[[Image:manager22.jpg\|link=\|1000px\|alt=]]		[[Image:manager22.jpg\|link=\|1000px\|alt=]]


	Once an attach event triggers, the attach event handler will be called and your code will run. In order to interact with the object, you need to cast it as the correct type and open it. You can determine the correct type by using <code>getChannelClassName()</code> (or the <code>channelClassName </code> property if you're using and object-oriented language). Once cast, you can open it and begin to use methods and properties that belong to that specific object. In the next section we'll look at an example of a program implementing the process described by this diagram.

	==Using the Phidget Manager==		==Using the Phidget Manager==

Chad: /* Object Structure */

2017-07-13T16:38:02Z

Object Structure

← Older revision		Revision as of 16:38, 13 July 2017
Line 5:		Line 5:

	It is important to understand the concepts of '''attach''' and '''detach''' as the they relate to the manager. A manager attach does not imply that a user channel has attached to a device channel, but that the device channel have become available. The device channel is now ready to be attached to a user channel. When a user channel closes and detaches from a device channel a manager event will not be fired. A manager '''detach''' event is fired when the Phidget device is removed from the system.		It is important to understand the concepts of '''attach''' and '''detach''' as the they relate to the manager. A manager attach does not imply that a user channel has attached to a device channel, but that the device channel have become available. The device channel is now ready to be attached to a user channel. When a user channel closes and detaches from a device channel a manager event will not be fired. A manager '''detach''' event is fired when the Phidget device is removed from the system.

	~~==Object Structure==~~

	~~You are probably already familiar with Phidgets software objects, where a single set of functions for a class of hardware are contained in one object. For example, the VoltageInput object:~~

	~~[[Image:voltageInput_object.jpg\|300px\|link=\|alt=]]~~

	The methods for the Phidget Manager are contained in the same way, but it does not belong to any particular Phidget device. It exists separately, so you can have an active Phidget Manager object even when there are no Phidgets attached.

	~~[[Image:manager.jpg\|300px\|link=\|alt=]]~~

	~~You can find the complete API for the Phidget Manager in the {{Phidget22API}}. Select your language from the first drop-down box and select '''Manager API''' from the second box.~~

	==Purpose==		==Purpose==