Language - REALBasic - Revision history

Cora at 21:03, 28 June 2012

2012-06-28T21:03:00Z

← Older revision		Revision as of 21:03, 28 June 2012
Line 17:		Line 17:

	Applications using Phidget can be developed in REALbasic through the C API. This tutorial assumes the use of REALbasic 2009, other recent versions should work as well and would be set up in a similar manner.		Applications using Phidget can be developed in REALbasic through the C API. This tutorial assumes the use of REALbasic 2009, other recent versions should work as well and would be set up in a similar manner.


	Phidgets will not run under REALbasic 2006. Although it’s possible to import Phidgets as ActiveX controls, this is not recommended due to the way REALbasic handles them.		Phidgets will not run under REALbasic 2006. Although it’s possible to import Phidgets as ActiveX controls, this is not recommended due to the way REALbasic handles them.

Cora at 21:02, 28 June 2012

2012-06-28T21:02:52Z

← Older revision		Revision as of 21:02, 28 June 2012
Line 3:		Line 3:
	==Support==		==Support==

	We no longer offer support for REALBasic Please select one of our [[Software Overview#Language Support\|supported languages]] to use your Phidget.		We no longer offer support for REALBasic.

			Please select one of our [[Software Overview#Language Support\|supported languages]] to use your Phidget.

	==Legacy Documentation==		==Legacy Documentation==

Cora at 21:02, 28 June 2012

2012-06-28T21:02:42Z

← Older revision		Revision as of 21:02, 28 June 2012
Line 2:		Line 2:
	{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}		{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}
	==Support==		==Support==
	~~REALBasic has a complete API for all Phidgets devices, but no sample code at this time. Essentially, a user can use our C libraries within RealBASIC.~~

	We no longer offer support for REALBasic Please select one of our [[Software Overview#Language Support\|supported languages]] to use your Phidget.		We no longer offer support for REALBasic Please select one of our [[Software Overview#Language Support\|supported languages]] to use your Phidget.

	~~If you would like to download our C libraries for your own use with REALBasic, please refer to the [[Software Overview#Operating System Support\|page for your operating system]].~~

	==Legacy Documentation==		==Legacy Documentation==

	Although we no longer offer support for REALBasic, our old documentation is below.		Although we no longer offer support for REALBasic, our old documentation is below.

			If you would like to download our C libraries for your own use with REALBasic, please refer to the [[Software Overview#Operating System Support\|page for your operating system]].
			REALBasic has a complete API for all Phidgets devices because it uses our C API, but it never had Phidget sample code.

	===Getting Started===		===Getting Started===

Cora at 21:01, 28 June 2012

2012-06-28T21:01:35Z

Cora at 21:01, 28 June 2012

2012-06-28T21:01:05Z

← Older revision		Revision as of 21:01, 28 June 2012
Line 2:		Line 2:
	{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}		{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}
	==Support==		==Support==
	REALBasic has a complete API for all Phidgets devices, but no sample code at this time.		REALBasic has a complete API for all Phidgets devices, but no sample code at this time. Essentially, a user can use our C libraries within RealBASIC.

	~~For a complete list~~ of our ~~supported languages and their support status,~~ [[~~Levels of~~ Support\|~~click here~~]].		We no longer offer support for REALBasic Please select one of our [[Software Overview#Language Support\|supported languages]] to use your Phidget.

	* Our honest opinion on how well this language is suited to ~~controlling Phidgets. If it is a poor choice~~, ~~suggest and link similar (better) languages.~~		If you would like to download our C libraries for your own use with REALBasic, please refer to the [[Software Overview#Operating System Support\|page for your operating system]].
	* In this section, list any restrictions or limitations that this particular language may impose. For example, incompatibility with certain operating ~~systems~~.

	==~~Development Environments and Compilers~~==		==Legacy Documentation==

	Describe each major compiler and notable differences or important information. (eg. framework versions) If there are known issues/workarounds mention them and link to the corresponding issue at the bottom of the page.		Although we no longer offer support for REALBasic, our old documentation is below.

	==~~Quick Downloads~~==		==Getting Started==
	~~Before you can run your program, you need to set up the proper environment and get the necessary files off the Phidgets website.~~
	~~Visit the drivers section at www.phidgets.com and get the latest:~~
	* [http://www.phidgets.com/drivers.php Phidget Framework]
	~~You will need the Phidget Framework to use and to program with Phidgets. We also recommend that you download the following reference materials:~~
	* [http://www.phidgets.com/documentation/Phidget21_C_Doc.zip API Manual]
	* [http://www.phidgets.com/documentation/web/cdoc/index.html API Reference]
	* We currently do not have any sample code for REALBasic.
	* You can find a high level discussion about programming with Phidgets in general on the [[General Phidget Programming]] page.
	* The [[Device Functionality]] page explains the general operational information for your device.

	~~You may want to have these pages open while working~~ through ~~these instructions~~.		Applications using Phidget can be developed in REALbasic through the C API. This tutorial assumes the use of REALbasic 2009, other recent versions should work as well and would be set up in a similar manner.

	~~==Getting Started==~~

	~~Applications using Phidget can be developed in REALbasic through the C API.~~
	~~This tutorial assumes the use of REALbasic 2009, other recent versions should work as well and would be set up in a similar manner.~~
	Phidgets will not run under REALbasic 2006. Although it’s possible to import Phidgets as ActiveX controls, this is not recommended due to the way REALbasic handles them.		Phidgets will not run under REALbasic 2006. Although it’s possible to import Phidgets as ActiveX controls, this is not recommended due to the way REALbasic handles them.
	To begin, launch REALbasic and create a new “Desktop Application”.
	Then, place an EditField “EditField1” in the form designer for the purpose of capturing some simple output.		To begin, launch REALbasic and create a new “Desktop Application”. Then, place an EditField “EditField1” in the form designer for the purpose of capturing some simple output.

	===Coding For Your Phidget===		===Coding For Your Phidget===
Line 148:		Line 135:
	For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would call CPhidgetRFID_create instead of CPhidgetInterfaceKit_create.		For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would call CPhidgetRFID_create instead of CPhidgetInterfaceKit_create.
	The methods and events available would change but they can be used in a similar manner.		The methods and events available would change but they can be used in a similar manner.

	~~==Building your Project==~~
	~~Describe the different ways a project could be built using this language.~~

	~~==Common Problems and Solutions/Workarounds==~~
	~~Here you can put various frequent problems and our recommended solutions.~~

Cora at 20:55, 28 June 2012

2012-06-28T20:55:58Z

← Older revision		Revision as of 20:55, 28 June 2012
Line 1:		Line 1:
	[[Category:~~Language~~]]		[[Category:LegacyLanguage]]
	{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}		{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}
	==Support==		==Support==

Cora: /* Quick Downloads */

2012-04-25T16:45:44Z

Quick Downloads

← Older revision		Revision as of 16:45, 25 April 2012
Line 21:		Line 21:
	* [http://www.phidgets.com/documentation/web/cdoc/index.html API Reference]		* [http://www.phidgets.com/documentation/web/cdoc/index.html API Reference]
	* We currently do not have any sample code for REALBasic.		* We currently do not have any sample code for REALBasic.
	* You can find a high level discussion about programming with Phidgets in general on the [[General ~~API~~]] page.		* You can find a high level discussion about programming with Phidgets in general on the [[General Phidget Programming]] page.
	* The [[Device Functionality]] page explains the general operational information for your device.		* The [[Device Functionality]] page explains the general operational information for your device.

Djrudiak at 17:38, 20 April 2012

2012-04-20T17:38:11Z

← Older revision		Revision as of 17:38, 20 April 2012
Line 1:		Line 1:
	[[Category:Language]]		[[Category:Language]]
	[[File:icon-REALBasic.png\|64x64px]] REALBasic is no longer maintained by Phidgets. ~~Preamble about the language's origin and its main characteristics.~~		{{OSLang\|[[File:icon-REALBasic.png\|64x64px\|alt=\|link=]]\|REALBasic is no longer maintained by Phidgets.}}

	==Support==		==Support==
	REALBasic has a complete API for all Phidgets devices, but no sample code at this time.		REALBasic has a complete API for all Phidgets devices, but no sample code at this time.

Mphi at 18:11, 19 April 2012

2012-04-19T18:11:07Z

← Older revision		Revision as of 18:11, 19 April 2012
Line 1:		Line 1:
	[[Category:Language]]		[[Category:Language]]
	[[File:icon-REALBasic.png\|64x64px]] Preamble about the language's origin and its main characteristics.		[[File:icon-REALBasic.png\|64x64px]] REALBasic is no longer maintained by Phidgets. Preamble about the language's origin and its main characteristics.

	==Support==		==Support==

Djrudiak: /* Getting Started */

2012-03-27T21:31:47Z

Getting Started

← Older revision		Revision as of 21:31, 27 March 2012
Line 40:		Line 40:
	For example, you can declare at initialization (inside Windows1.Open) some C functions for a PhidgetInterfaceKit with the following syntax:		For example, you can declare at initialization (inside Windows1.Open) some C functions for a PhidgetInterfaceKit with the following syntax:

	<div ~~style~~="~~background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;~~">		<div class="source"><syntaxhighlight lang=vb>
	<~~font size="3">~~
	~~<source~~ lang=vb>

	Declare Function CPhidget_open lib "phidget21" (phid as Ptr, serialNumber as Integer) as integer		Declare Function CPhidget_open lib "phidget21" (phid as Ptr, serialNumber as Integer) as integer
Line 49:		Line 47:
	Declare Function CPhidgetInterfaceKit_set_OnSensorChange_Handler lib "phidget21"(CPhidgetInterfaceKitHandle as Ptr, fptr as Ptr, UserPtr as Ptr) as Integer		Declare Function CPhidgetInterfaceKit_set_OnSensorChange_Handler lib "phidget21"(CPhidgetInterfaceKitHandle as Ptr, fptr as Ptr, UserPtr as Ptr) as Integer

	</~~source~~>		</syntaxhighlight></div>
	~~</font>~~
	</div>

	The declaration closely follows the C API with a few minor changes.		The declaration closely follows the C API with a few minor changes.
Line 60:		Line 56:
	This can be done by declaring a property on Windows1 named “ifKitHandle” as a Ptr, calling create on an empty block of memory, and then setting the handle to the result.		This can be done by declaring a property on Windows1 named “ifKitHandle” as a Ptr, calling create on an empty block of memory, and then setting the handle to the result.

	<div ~~style~~="~~background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;~~">		<div class="source"><syntaxhighlight lang=vb>
	<~~font size="3">~~
	~~<source~~ lang=vb>

	Dim tmp As MemoryBlock		Dim tmp As MemoryBlock
Line 70:		Line 64:
	ifKitHandle = tmp.Ptr(0)		ifKitHandle = tmp.Ptr(0)

	</~~source~~>		</syntaxhighlight></div>
	~~</font>~~
	</div>

	The object name for any type of Phidget is listed in the API manual.		The object name for any type of Phidget is listed in the API manual.
Line 85:		Line 77:
	WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.		WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.

	<div ~~style~~="~~background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;~~">		<div class="source"><syntaxhighlight lang=vb>
	<~~font size="3">~~
	~~<source~~ lang=vb>

	result = CPhidget_open(ifKitHandle, -1)		result = CPhidget_open(ifKitHandle, -1)
Line 96:		Line 86:
	end if		end if

	</~~source~~>		</syntaxhighlight></div>
	~~</font>~~
	</div>

	The different parameters and open calls can be used to open the first Phidget of a type it can find, open based on a serial number, or even open across the network.		The different parameters and open calls can be used to open the first Phidget of a type it can find, open based on a serial number, or even open across the network.
Line 112:		Line 100:
	Event handler methods with matching definitions must be created inside their own module (Project \| Add \| Module).		Event handler methods with matching definitions must be created inside their own module (Project \| Add \| Module).

	<div ~~style~~="~~background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;~~">		<div class="source"><syntaxhighlight lang=vb>
	<~~font size="3">~~
	~~<source~~ lang=vb>

	Function ifKit_OnSensorChange(ByVal phid As Ptr, ByVal userPtr As Ptr, ByVal index		Function ifKit_OnSensorChange(ByVal phid As Ptr, ByVal userPtr As Ptr, ByVal index
Line 122:		Line 108:
	End Function		End Function

	</~~source~~>		</syntaxhighlight></div>
	~~</font>~~
	</div>

	In this example, a new module “Module1” was created and given the ifKit_OnSensorChange method.		In this example, a new module “Module1” was created and given the ifKit_OnSensorChange method.
Line 130:		Line 114:
	Inside Window1.Open we can then link to the method we wrote with a call to CPhidgetInterfaceKit_set_OnSensorChange_Handler.		Inside Window1.Open we can then link to the method we wrote with a call to CPhidgetInterfaceKit_set_OnSensorChange_Handler.

	<div ~~style~~="~~background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;~~">		<div class="source"><syntaxhighlight lang=vb>
	<~~font size="3">~~
	~~<source~~ lang=vb>

	Call CPhidgetInterfaceKit_set_OnSensorChange_Handler(ifKitHandle, AddressOf Module1.ifKit_OnsensorChange, nil)		Call CPhidgetInterfaceKit_set_OnSensorChange_Handler(ifKitHandle, AddressOf Module1.ifKit_OnsensorChange, nil)

	</~~source~~>		</syntaxhighlight></div>
	~~</font>~~
	</div>

	With this, the code inside ifKit_onSensorChange will get executed every time the PhidgetInterfaceKit reports a change on one of its analog inputs.		With this, the code inside ifKit_onSensorChange will get executed every time the PhidgetInterfaceKit reports a change on one of its analog inputs.
Line 149:		Line 129:
	Simply declare the C function before using calls such as CPhidgetInterfaceKit_getSensorValue for PhidgetInterfaceKits.		Simply declare the C function before using calls such as CPhidgetInterfaceKit_getSensorValue for PhidgetInterfaceKits.

	<div ~~style~~="~~background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;~~">		<div class="source"><syntaxhighlight lang=vb>
	<~~font size="3">~~
	~~<source~~ lang=vb>

	Declare Function CPhidgetInterfaceKit_getSensorValue lib "phidget21" (phid as Ptr, index as Integer, sensorValue as Ptr) as Integerresult = CPhidgetInterfaceKit_getSensorValue(ifKitHandle, 0, tmp)		Declare Function CPhidgetInterfaceKit_getSensorValue lib "phidget21" (phid as Ptr, index as Integer, sensorValue as Ptr) as Integerresult = CPhidgetInterfaceKit_getSensorValue(ifKitHandle, 0, tmp)
Line 157:		Line 135:
	Window1.EditField1.Text = Str(sensorValue)		Window1.EditField1.Text = Str(sensorValue)

	</~~source~~>		</syntaxhighlight></div>
	~~</font>~~
	</div>

	===Working with multiple Phidgets===		===Working with multiple Phidgets===
Line 172:		Line 148:
	The design given in this document can also be followed for almost all Phidgets.		The design given in this document can also be followed for almost all Phidgets.
	For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would call CPhidgetRFID_create instead of CPhidgetInterfaceKit_create.		For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would call CPhidgetRFID_create instead of CPhidgetInterfaceKit_create.
	The methods and events available would change but they can be used in a similar manner.		The methods and events available would change but they can be used in a similar manner.

	==Building your Project==		==Building your Project==

← Older revision		Revision as of 21:01, 28 June 2012
Line 12:		Line 12:
	Although we no longer offer support for REALBasic, our old documentation is below.		Although we no longer offer support for REALBasic, our old documentation is below.

	==Getting Started==		===Getting Started===

	Applications using Phidget can be developed in REALbasic through the C API. This tutorial assumes the use of REALbasic 2009, other recent versions should work as well and would be set up in a similar manner.		Applications using Phidget can be developed in REALbasic through the C API. This tutorial assumes the use of REALbasic 2009, other recent versions should work as well and would be set up in a similar manner.
Line 21:		Line 21:
	To begin, launch REALbasic and create a new “Desktop Application”. Then, place an EditField “EditField1” in the form designer for the purpose of capturing some simple output.		To begin, launch REALbasic and create a new “Desktop Application”. Then, place an EditField “EditField1” in the form designer for the purpose of capturing some simple output.

	===Coding For Your Phidget===		====Coding For Your Phidget====

	Before you can use the Phidget, you must declare each of the functions from the C library that the program will use.		Before you can use the Phidget, you must declare each of the functions from the C library that the program will use.
Line 55:		Line 55:
	Every type of Phidget also inherits functionality from the Phidget base class.		Every type of Phidget also inherits functionality from the Phidget base class.

	===Connecting to the Phidget===		====Connecting to the Phidget====

	The program can try to connect to the Phidget through an open call.		The program can try to connect to the Phidget through an open call.
Line 80:		Line 80:
	The one connection per device limit does not apply when exclusively using the Phidget Webservice.		The one connection per device limit does not apply when exclusively using the Phidget Webservice.

	===Event Driven Programming===		====Event Driven Programming====

	We recommend the use of event driven programming when working with Phidgets.		We recommend the use of event driven programming when working with Phidgets.
Line 110:		Line 110:
	Please refer to the API manual for a full list of events and their usage.		Please refer to the API manual for a full list of events and their usage.

	===Working directly with the Phidget===		====Working directly with the Phidget====

	Some values can be directly read and set on the Phidget, and inside polling loops used as an alternative to event driven programming.		Some values can be directly read and set on the Phidget, and inside polling loops used as an alternative to event driven programming.
Line 123:		Line 123:
	</syntaxhighlight></div>		</syntaxhighlight></div>

	===Working with multiple Phidgets===		====Working with multiple Phidgets====

	Multiple Phidgets of the same type can easily be run inside the same program.		Multiple Phidgets of the same type can easily be run inside the same program.
Line 130:		Line 130:
	If the application needs to distinguish between the devices, open can be called with the serial number of a specific Phidget.		If the application needs to distinguish between the devices, open can be called with the serial number of a specific Phidget.

	===Other Phidgets===		====Other Phidgets====

	The design given in this document can also be followed for almost all Phidgets.		The design given in this document can also be followed for almost all Phidgets.
	For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would call CPhidgetRFID_create instead of CPhidgetInterfaceKit_create.		For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would call CPhidgetRFID_create instead of CPhidgetInterfaceKit_create.
	The methods and events available would change but they can be used in a similar manner.		The methods and events available would change but they can be used in a similar manner.