Language - Adobe Director - Revision history

Mparadis at 18:54, 6 June 2017

2017-06-06T18:54:45Z

← Older revision		Revision as of 18:54, 6 June 2017
Line 11:		Line 11:
	{{QuickDownloads\|Adobe Director\|		{{QuickDownloads\|Adobe Director\|
	{{APIQuickDownloads\|{{SERVER}}/documentation/COM_API_Manual.pdf}}\|		{{APIQuickDownloads\|{{SERVER}}/documentation/COM_API_Manual.pdf}}\|
	{{ExampleQuickDownloads\|{{SERVER}}/downloads/examples/AdobeDirector.zip\|}}\|		{{ExampleQuickDownloads\|{{SERVER}}/downloads/phidget21/examples/com/AdobeDirector.zip\|}}\|
	{{ExtraLibraryQuickDownloads\|{{SERVER}}/downloads/libraries/Phidget21-windevel.zip\|COM\|}}		{{ExtraLibraryQuickDownloads\|{{SERVER}}/downloads/phidget21/libraries/windows/Phidget21-windevel.zip\|COM\|}}
	{{WindowsQuickDownloads}}}}		{{WindowsQuickDownloads}}}}

Line 27:		Line 27:
	Adobe Director programs on Windows depend on the following:		Adobe Director programs on Windows depend on the following:
	* <b>{{Code\|phidget21.dll}}</b> contains the actual Phidget library, which is used at run-time. By default, it is placed in {{Code\|C:\Windows\System32}}. The installers in the [[#Libraries and Drivers \| Quick Downloads]] section put this file into your system.		* <b>{{Code\|phidget21.dll}}</b> contains the actual Phidget library, which is used at run-time. By default, it is placed in {{Code\|C:\Windows\System32}}. The installers in the [[#Libraries and Drivers \| Quick Downloads]] section put this file into your system.
	* <b>{{Code\|Phidget21COM.dll}}</b> is the Component Object Model (COM) library and provides your project access to the Phidget ActiveX objects. This is part of our [{{SERVER}}/downloads/libraries/Phidget21-windevel.zip COM Library]. If you installed the Phidget drivers, it will have automatically registered the ActiveX objects into your system. If you are manually installing this file, you must register it through command line by running: {{Code\|regsvr32 Phidget21COM.dll}}.		* <b>{{Code\|Phidget21COM.dll}}</b> is the Component Object Model (COM) library and provides your project access to the Phidget ActiveX objects. This is part of our [{{SERVER}}/downloads/phidget21/libraries/windows/Phidget21-windevel.zip COM Library]. If you installed the Phidget drivers, it will have automatically registered the ActiveX objects into your system. If you are manually installing this file, you must register it through command line by running: {{Code\|regsvr32 Phidget21COM.dll}}.

	If you do not want to use our installer, you can download both [{{SERVER}}/downloads/libraries/Phidget21-windevel.zip files] and manually install them where you want; refer to our [[OS_-_Windows#Manual_File_Installation\| Manual Installation Instructions]].		If you do not want to use our installer, you can download both [{{SERVER}}/downloads/phidget21/libraries/windows/Phidget21-windevel.zip files] and manually install them where you want; refer to our [[OS_-_Windows#Manual_File_Installation\| Manual Installation Instructions]].

	===Adobe Director 11.5===		===Adobe Director 11.5===
Line 35:		Line 35:
	====Use Our Examples====		====Use Our Examples====

	1. Download the [{{SERVER}}/downloads/examples/AdobeDirector.zip examples] and unpack them into a folder. These examples were written in Adobe Director 11.5.		1. Download the [{{SERVER}}/downloads/phidget21/examples/com/AdobeDirector.zip examples] and unpack them into a folder. These examples were written in Adobe Director 11.5.

	2. The easiest way to confirm that your environment is set up properly will be to run the HelloWorld Adobe Director example. In the Adobe Director environment, open up the file named {{Code\|HelloWorld.dir}}.		2. The easiest way to confirm that your environment is set up properly will be to run the HelloWorld Adobe Director example. In the Adobe Director environment, open up the file named {{Code\|HelloWorld.dir}}.

Burley: /* Windows (2000/XP/Vista/7) */

2013-04-02T18:33:35Z

Windows (2000/XP/Vista/7)

← Older revision		Revision as of 18:33, 2 April 2013
Line 22:		Line 22:
	The only operating system we support with Adobe Director is [[#Windows (2000/XP/Vista/7)\|Windows (2000/XP/Vista/7)]].		The only operating system we support with Adobe Director is [[#Windows (2000/XP/Vista/7)\|Windows (2000/XP/Vista/7)]].

	==Windows (~~2000/~~XP/Vista/7)==		==Windows (XP/Vista/7/8)==

	===Description of Library Files===		===Description of Library Files===

Burley: /* Windows users in The Netherlands */

2012-08-08T17:59:51Z

Windows users in The Netherlands

← Older revision		Revision as of 17:59, 8 August 2012
Line 166:		Line 166:
	===Windows users in The Netherlands===		===Windows users in The Netherlands===

	A number of users in the Netherlands have reported issues with running our example code. It is possible this is an issue related to the language pack used for Windows however, we do not currently really know why. As we aren't able to run a Dutch version of Windows here, it is difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].		A number of users in the Netherlands have reported issues with running our example code. It is possible this is an issue related to the Dutch language pack used for Windows however, we do not currently really know why. As we aren't able to run a Dutch version of Windows here, it is difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].

Burley: /* Windows users in Netherlands: The examples are mislukken */

2012-08-08T17:59:29Z

Windows users in Netherlands: The examples are mislukken

← Older revision		Revision as of 17:59, 8 August 2012
Line 164:		Line 164:
	==Common Problems and Solutions/Workarounds==		==Common Problems and Solutions/Workarounds==

	===Windows users in Netherlands~~: The examples are mislukken~~===		===Windows users in The Netherlands===

	A number of users in the Netherlands have reported issues with running our example code. It is possible this is an issue related to the language pack used for Windows however, we do not currently really know why. As we aren't able to run a Dutch version of Windows here, it is difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].		A number of users in the Netherlands have reported issues with running our example code. It is possible this is an issue related to the language pack used for Windows however, we do not currently really know why. As we aren't able to run a Dutch version of Windows here, it is difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].

Burley: /* Windows users in Netherlands: The examples are mislukken */

2012-08-08T17:57:33Z

Windows users in Netherlands: The examples are mislukken

← Older revision		Revision as of 17:57, 8 August 2012
Line 166:		Line 166:
	===Windows users in Netherlands: The examples are mislukken===		===Windows users in Netherlands: The examples are mislukken===

	~~Our examples are unsupported to all~~ users in the ~~country of~~ Netherlands. ~~Sorry!~~ We do not currently know why~~; a Director version problem is suspected~~. As we aren't able to run a ~~Netherlands~~ version ~~outside~~ of ~~the Netherlands~~, ~~this makes the problem very~~ difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].		A number of users in the Netherlands have reported issues with running our example code. It is possible this is an issue related to the language pack used for Windows however, we do not currently really know why. As we aren't able to run a Dutch version of Windows here, it is difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].

Burley: /* Step Three: Do Things with the Phidget */

2012-08-08T17:36:41Z

Step Three: Do Things with the Phidget

← Older revision		Revision as of 17:36, 8 August 2012
Line 150:		Line 150:
	</div>		</div>

	Other events for different Phidgets can be found in the ~~devices~~ [[:Category:UserGuide\|user guide]], and in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual.		Other events for different Phidgets can be found in the device's [[:Category:UserGuide\|user guide]], and in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual.

	====Step Four: Close and Delete====		====Step Four: Close and Delete====

Burley: /* Step Three: Do Things with the Phidget */

2012-08-08T17:36:33Z

Step Three: Do Things with the Phidget

← Older revision		Revision as of 17:36, 8 August 2012
Line 150:		Line 150:
	</div>		</div>

	Other events for different Phidgets can be found on the ~~device product page on our~~ [~~{{SERVER}} main website~~], and in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual.		Other events for different Phidgets can be found in the devices [[:Category:UserGuide\|user guide]], and in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual.

	====Step Four: Close and Delete====		====Step Four: Close and Delete====

Cora: /* Common Problems and Solutions/Workarounds */

2012-06-28T19:21:02Z

Common Problems and Solutions/Workarounds

← Older revision		Revision as of 19:21, 28 June 2012
Line 164:		Line 164:
	==Common Problems and Solutions/Workarounds==		==Common Problems and Solutions/Workarounds==

	===~~{{ProblemSolution\|~~Windows users in Netherlands\|The examples are mislukken}}===		===Windows users in Netherlands: The examples are mislukken===

	Our examples are unsupported to all users in the country of Netherlands. Sorry! We do not currently know why; a Director version problem is suspected. As we aren't able to run a Netherlands version outside of the Netherlands, this makes the problem very difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].		Our examples are unsupported to all users in the country of Netherlands. Sorry! We do not currently know why; a Director version problem is suspected. As we aren't able to run a Netherlands version outside of the Netherlands, this makes the problem very difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].

Cora at 19:20, 28 June 2012

2012-06-28T19:20:33Z

← Older revision		Revision as of 19:20, 28 June 2012
Line 100:		Line 100:
	It may help to have the [[General Phidget Programming]] page and this section open at the same time, because they parallel each other and you can refer to the Adobe Director syntax. However, many additional concepts are covered on the General Phidget Programming page on a high level, such as using multiple Phidgets, handling errors, and different styles of programming.		It may help to have the [[General Phidget Programming]] page and this section open at the same time, because they parallel each other and you can refer to the Adobe Director syntax. However, many additional concepts are covered on the General Phidget Programming page on a high level, such as using multiple Phidgets, handling errors, and different styles of programming.

	For example, if we were using a [~~[Product -~~ 1018 ~~- PhidgetInterfaceKit 8/8/8 \|~~ Phidget Interface Kit]] as our device, the general calls would look like this:		For example, if we were using a [{{SERVER}}/products.php?product_id=1018 Phidget Interface Kit] as our device, the general calls would look like this:

	====Step One: Initialize and Open====		====Step One: Initialize and Open====

Cora at 19:19, 28 June 2012

2012-06-28T19:19:59Z

← Older revision		Revision as of 19:19, 28 June 2012
Line 10:		Line 10:

	{{QuickDownloads\|Adobe Director\|		{{QuickDownloads\|Adobe Director\|
	{{APIQuickDownloads\|~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf}}\|		{{APIQuickDownloads\|{{SERVER}}/documentation/COM_API_Manual.pdf}}\|
	{{ExampleQuickDownloads\|~~http://www.phidgets.com~~/downloads/examples/AdobeDirector.zip\|}}\|		{{ExampleQuickDownloads\|{{SERVER}}/downloads/examples/AdobeDirector.zip\|}}\|
	{{ExtraLibraryQuickDownloads\|~~http://www.phidgets.com~~/downloads/libraries/Phidget21-windevel.zip\|COM\|}}		{{ExtraLibraryQuickDownloads\|{{SERVER}}/downloads/libraries/Phidget21-windevel.zip\|COM\|}}
	{{WindowsQuickDownloads}}		{{WindowsQuickDownloads}}}}
	}}

	==Getting started with Adobe Director==		==Getting started with Adobe Director==
Line 28:		Line 27:
	Adobe Director programs on Windows depend on the following:		Adobe Director programs on Windows depend on the following:
	* <b>{{Code\|phidget21.dll}}</b> contains the actual Phidget library, which is used at run-time. By default, it is placed in {{Code\|C:\Windows\System32}}. The installers in the [[#Libraries and Drivers \| Quick Downloads]] section put this file into your system.		* <b>{{Code\|phidget21.dll}}</b> contains the actual Phidget library, which is used at run-time. By default, it is placed in {{Code\|C:\Windows\System32}}. The installers in the [[#Libraries and Drivers \| Quick Downloads]] section put this file into your system.
	* <b>{{Code\|Phidget21COM.dll}}</b> is the Component Object Model (COM) library and provides your project access to the Phidget ActiveX objects. This is part of our [~~http://www.phidgets.com~~/downloads/libraries/Phidget21-windevel.zip COM Library]. If you installed the Phidget drivers, it will have automatically registered the ActiveX objects into your system. If you are manually installing this file, you must register it through command line by running: {{Code\|regsvr32 Phidget21COM.dll}}.		* <b>{{Code\|Phidget21COM.dll}}</b> is the Component Object Model (COM) library and provides your project access to the Phidget ActiveX objects. This is part of our [{{SERVER}}/downloads/libraries/Phidget21-windevel.zip COM Library]. If you installed the Phidget drivers, it will have automatically registered the ActiveX objects into your system. If you are manually installing this file, you must register it through command line by running: {{Code\|regsvr32 Phidget21COM.dll}}.

	If you do not want to use our installer, you can download both [~~http://www.phidgets.com~~/downloads/libraries/Phidget21-windevel.zip files] and manually install them where you want; refer to our [[OS_-_Windows#Manual_File_Installation\| Manual Installation Instructions]].		If you do not want to use our installer, you can download both [{{SERVER}}/downloads/libraries/Phidget21-windevel.zip files] and manually install them where you want; refer to our [[OS_-_Windows#Manual_File_Installation\| Manual Installation Instructions]].

	===Adobe Director 11.5===		===Adobe Director 11.5===
Line 36:		Line 35:
	====Use Our Examples====		====Use Our Examples====

	1. Download the [~~http://www.phidgets.com~~/downloads/examples/AdobeDirector.zip examples] and unpack them into a folder. These examples were written in Adobe Director 11.5.		1. Download the [{{SERVER}}/downloads/examples/AdobeDirector.zip examples] and unpack them into a folder. These examples were written in Adobe Director 11.5.

	2. The easiest way to confirm that your environment is set up properly will be to run the HelloWorld Adobe Director example. In the Adobe Director environment, open up the file named {{Code\|HelloWorld.dir}}.		2. The easiest way to confirm that your environment is set up properly will be to run the HelloWorld Adobe Director example. In the Adobe Director environment, open up the file named {{Code\|HelloWorld.dir}}.
Line 84:		Line 83:
	Your main reference for writing Adobe Director code will be our Adobe Director API information, with syntax for all of our functions:		Your main reference for writing Adobe Director code will be our Adobe Director API information, with syntax for all of our functions:

	{{UsingAPhidgetInCodeGeneral\|both of which are available in Adobe Director\|[~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API]}}		{{UsingAPhidgetInCodeGeneral\|both of which are available in Adobe Director\|[{{SERVER}}/documentation/COM_API_Manual.pdf COM API]}}

	===Example Flow===		===Example Flow===

	{{ExamplePseudocode\|In Adobe Director, you catch these '''event''' functions using their specific names as shown below in the Code Snippets section. The specific syntax for different events and which Phidgets you can catch which events for can be found in the [~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API] manual. Catching events by name hooks your event functions into the actual events when they occur. <br>		{{ExamplePseudocode\|In Adobe Director, you catch these '''event''' functions using their specific names as shown below in the Code Snippets section. The specific syntax for different events and which Phidgets you can catch which events for can be found in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual. Catching events by name hooks your event functions into the actual events when they occur. <br>
	In the example code, some event functions are common to all Phidgets. These are events such as '''OnAttach''' and '''OnDetach''', etc.<br><br>		In the example code, some event functions are common to all Phidgets. These are events such as '''OnAttach''' and '''OnDetach''', etc.<br><br>
	Some event functions will be specific to each device, like when a tag is read on an RFID board, or when a sensor value changes on an Interface Kit.		Some event functions will be specific to each device, like when a tag is read on an RFID board, or when a sensor value changes on an Interface Kit.
	\|Creating a Phidget software object in Adobe Director is specific to the Phidget. For a Phidget Spatial, for example, this would involve creating a {{Code\|Spatial}} ActiveX object, as shown in the [[#Write Your Own Code\|Write Your Own Code]] section above. The examples show working instances of how to do this, and how to use other API functions.<br><br>		\|Creating a Phidget software object in Adobe Director is specific to the Phidget. For a Phidget Spatial, for example, this would involve creating a {{Code\|Spatial}} ActiveX object, as shown in the [[#Write Your Own Code\|Write Your Own Code]] section above. The examples show working instances of how to do this, and how to use other API functions.<br><br>
	The object provides device specific methods and properties which are available from the API for your specific Phidget.\|		The object provides device specific methods and properties which are available from the API for your specific Phidget.\|
	[~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API]}}		[{{SERVER}}/documentation/COM_API_Manual.pdf COM API]}}

	===Code Snippets===		===Code Snippets===
Line 112:		Line 111:
	* A Phidget across the network.		* A Phidget across the network.

	The [~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API] manual lists all of the available modes that open provides. One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed. This prevents any other instances from retrieving data from the Phidget, including other programs. The one connection per device limit does not apply when exclusively using the [[Phidget WebService]].		The [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual lists all of the available modes that open provides. One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed. This prevents any other instances from retrieving data from the Phidget, including other programs. The one connection per device limit does not apply when exclusively using the [[Phidget WebService]].

	====Step Two: Wait for Attachment (plugging in) of the Phidget====		====Step Two: Wait for Attachment (plugging in) of the Phidget====
Line 141:		Line 140:
	</div>		</div>

	With this method, the code inside OnSensorChange will get executed every time the InterfaceKit reports a change on one of its analog inputs. Please refer to the [~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API] manual for a full list of events and their usage.		With this method, the code inside OnSensorChange will get executed every time the InterfaceKit reports a change on one of its analog inputs. Please refer to the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual for a full list of events and their usage.

	Some values can be directly read and set on the Phidget, and inside polling loops used as an alternative to event driven programming. Simply use the CallString method for obtaining data such as SensorValue(Index) or OutputState(Index, OutputState) for Interface Kits. For example:		Some values can be directly read and set on the Phidget, and inside polling loops used as an alternative to event driven programming. Simply use the CallString method for obtaining data such as SensorValue(Index) or OutputState(Index, OutputState) for Interface Kits. For example:
Line 151:		Line 150:
	</div>		</div>

	Other events for different Phidgets can be found on the device product page on our [~~http://www.phidgets.com~~ main website], and in the [~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API] manual.		Other events for different Phidgets can be found on the device product page on our [{{SERVER}} main website], and in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API] manual.

	====Step Four: Close and Delete====		====Step Four: Close and Delete====
Line 161:		Line 160:
	Multiple Phidgets of the same type can easily be run inside the same Adobe Director program. This requires another PhidgetInterfaceKit ActiveX object to be created and placed. The new object can then be set up, opened and used in the same process as the previous one. If the application needs to distinguish between the devices, open can be called with the serial number of a specific Phidget.		Multiple Phidgets of the same type can easily be run inside the same Adobe Director program. This requires another PhidgetInterfaceKit ActiveX object to be created and placed. The new object can then be set up, opened and used in the same process as the previous one. If the application needs to distinguish between the devices, open can be called with the serial number of a specific Phidget.

	The complete set of functions you have available for all Phidgets can be found in the [~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API].		The complete set of functions you have available for all Phidgets can be found in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API].

	==Common Problems and Solutions/Workarounds==		==Common Problems and Solutions/Workarounds==
Line 167:		Line 166:
	==={{ProblemSolution\|Windows users in Netherlands\|The examples are mislukken}}===		==={{ProblemSolution\|Windows users in Netherlands\|The examples are mislukken}}===

	Our examples are unsupported to all users in the country of Netherlands. Sorry! We do not currently know why; a Director version problem is suspected. As we aren't able to run a Netherlands version outside of the Netherlands, this makes the problem very difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please ~~contact us~~.		Our examples are unsupported to all users in the country of Netherlands. Sorry! We do not currently know why; a Director version problem is suspected. As we aren't able to run a Netherlands version outside of the Netherlands, this makes the problem very difficult to debug. If you would like to help us work through the example code that we provide and help us figure out why, please [[Contact Us]].