Notice: This page contains information for the legacy Phidget21 Library. Phidget21 does not support VINT Phidgets, and will not support any new Phidgets. Phidget21 will be maintained until 2020. We recommend that new projects be developed against the Phidget22 Library.
Difference between revisions of "Language - Adobe Director"
(→Description of Library)
|Line 1:||Line 1:|
[[File:icon-Adobe_Director.png|64x64px|link=|alt=]]Adobe Director, developed by [http://www.adobe.com Adobe Systems] is a tool used to build interactive and multimedia applications.
Revision as of 17:20, 20 April 2012
|Adobe Director, developed by Adobe Systems is a tool used to build interactive and multimedia applications.|
- 1 Introduction
- 2 Quick Downloads
- 3 Getting started with Adobe Director
- 4 Windows (2000/XP/Vista/7)
- 5 Follow the Examples
- 6 Code Snippets
- 7 Common Problems and Solutions/Workarounds
If this is your first time working with a Phidget, we suggest starting with the Getting Started page for your specific device. This can be found in the user guide for your device. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use Adobe Director specifically.
Adobe Director is capable of using the complete Phidget API, including events. We also provide example code in Adobe Director for the PhidgetInterfaceKit devices.
Adobe Director can be developed with Windows..
You can compare Adobe Director with our other supported languages.
Just need the Adobe Director documentation, drivers, libraries, and examples? Here they are:
Libraries and Drivers
- COM Libraries
- 32-bit Windows Drivers Installer
- 64-bit Windows Drivers Installer
- Windows Driver and Library Files (Zipped)
Getting started with Adobe Director
If you are new to writing code for Phidgets, we recommend starting by running, then modifying existing examples. This will allow you to:
- Make sure your libraries are properly linked
- Go from source code to a test application as quickly as possible
- Ensure your Phidget is hooked up properly
Description of Library
Adobe Director programs on Windows depend on the following. The installers in the Quick Downloads section put only the
phidget21.dll into your system.
phidget21.dllcontains the actual Phidget library, which is used at run-time. By default, it is placed in
Phidget21COM.dllis the Component Object Model(COM) library and provides your project access to the Phidget ActiveX objects. 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:
Adobe Director 11.5
Use Our Examples
1. Download the 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
3. To run the example, click on Control → Play.
4. This program will detect for devices that are attached/detached on the computer. Go ahead, and attach or detach your devices! Here is an example output:
After confirming that the
HelloWorld example is working, you can proceed to run the example for your device. Currently, the only device we have example code for is the PhidgetInterfaceKit.
Once you have the Adobe Director examples running, we have a teaching section below to help you follow them.
Write Your Own Code
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your environment to properly link the Phidget ActiveX object.
1. Create a new movie.
2. Navigate to Insert → Control → ActiveX.
3. Select the ActiveX control that corresponds to your device. Select
4. A window will pop up listing the properties and methods of the ActiveX class. Select
5. The ActiveX class will be added to your cast. Create an instance of it by dragging and dropping the cast member onto the stage.
The project now has access to the Phidget function calls and you are ready to begin coding.
The same teaching section which describes the examples also has further resources for programming your Phidget.
Follow the Examples
By following the instructions for your operating system and compiler above, you probably now have a working example and want to understand it better so you can change it to do what you want. This teaching section has resources for you to learn from the examples and write your own.
Next, comes our API information. These resources outline the Adobe Director Phidget functions:
- COM API (This is the complete set of functions you have available for all Phidgets)
- Device Specific APIs - The one for your Phidget can be found in its user guide.
To learn the details behind opening, configuring, using, and closing your Phidget, try the General Phidget Programming page. That page also describes using the Phidget in an event-driven manner and in a traditional manner, both of which are available in Adobe Director.
The Hello World example has this general structure so you can follow along. We also have an in-depth general introduction to writing Phidget code (like open, read data, etc), as well as the COM API for specific syntax:
// ----- Event and Other Functions -----
Create any Language-Specific Functions (exception handling)
Create General Attach, Detach, and Error Handling Functions:
In Adobe Director, you can name these event functions whatever you like. You will then pass them as function pointers to the Phidget library below in the Main Code section. This hooks them into the actual events when they occur.
// ----- Main Code -----
Creating a Phidget software object in Adobe Director is specific to the Phidget. For a Phidget Spatial, for example, this would involve creating a
Common Problems and Solutions/Workarounds
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.