|
|
(12 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
| <metadesc>Communicate over USB with sensors, controllers and relays with Phidgets! Our Swift library supports iOS using Xcode.</metadesc>
| | [[Category:Language]] |
| == Quick Downloads ==
| | __NOTOC__ |
|
| |
|
| Already know what you're doing? Here you go:
| | We provide support for the Swift language on macOS. We also provide instructions on how to get your project started in Xcode for use in '''macOS''' and '''iOS''' applications. Select your operating system below, and follow the instructions to get your project running with Phidgets. |
|
| |
|
| === Documentation ===
| | Once you have set up your development environment to run with Phidgets, we recommend you follow our guide on [[Phidget Programming Basics]]. The guide will showcase the fundamentals of programming with Phidgets. |
|
| |
|
| *{{Phidget22API}} (select C from the drop-down menu)
| | ==Setup Guide== |
|
| |
|
| === Example Code === | | <div class="phd-deck-sequence"> |
| | __NOTOC__ |
| | {{PT3_SWIFT_CHOOSE}}{{PT3_SWIFT_MAC_XCODE}}{{PT3_SWIFT_MAC_XCODE_1}}{{PT3_SWIFT_MAC_XCODE_2}}{{PT3_SWIFT_IOS_XCODE}}{{PT3_SWIFT_IOS_XCODE_1}}{{PT3_SWIFT_IOS_XCODE_2}} |
| | </div> |
|
| |
|
| *{{SampleCode|Swift|Swift Examples}}
| |
|
| |
|
| === Libraries === | | == Quick Downloads == |
|
| |
|
| {{MacQuickDownloads}}
| | If you already know what you're doing and just need the files, you can find them all below. |
| {{iOSQuickDownloads}}
| |
|
| |
|
| == Getting Started with Swift == | | === Documentation === |
| Welcome to using Phidgets with Swift! By using Swift, you will have access to the complete {{Phidget22API}}, including events. We also provide example code in Swift for multiple Phidget classes.
| |
|
| |
|
| == iOS ==
| | *{{Phidget22API}} (select Swift from the drop-down menu) |
| {{IOS_Languages}} | |
| ===Xcode===
| |
| ====Use Our Examples====
| |
| One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples for iOS you will need to download [https://developer.apple.com/xcode/ Xcode] from the Mac App Store.
| |
|
| |
|
| | === Example Code === |
|
| |
|
| Now that you have Xcode installed, download the Swift example:
| | *{{SampleCode|Swift|Swift Examples}} |
| *{{SampleCode|Swift|Swift Example}} | |
| | |
| | |
| You have previously downloaded the Phidget iOS libraries on the iOS page, but here they are again, just in case:
| |
| *[{{SERVER}}/downloads/phidget22/libraries/ios/Phidget22_iOS.zip Phidget iOS Libraries]
| |
| | |
| | |
| Next, unpack the Swift example and navigate to ''Phidget.xcodeproj''. Open the file in Xcode:
| |
| [[Image:Swift_open.png|link=|center]]
| |
| | |
| | |
| {{IOS_use_our_examples}}
| |
| | |
| ====Configure Your Project====
| |
| Whether you are building a project from scratch, or adding Phidget functionality to an existing project, you will need to configure your development environment to properly link the Phidget libraries. To begin:
| |
| | |
| Create a new Xcode project:
| |
| [[Image:Cocoa_CreateProject.png |link=|center]]
| |
| | |
| | |
| Next, select an iOS application. For this tutorial's purposes, we will use a Single View Application:
| |
| [[Image:iOS_SingleView.png |link=|center]]
| |
| | |
| | |
| Name the project, select Swift as the language, and choose which devices will be supported:
| |
| [[Image:iOS_NameProject_Swift.png|link=|center]]
| |
| | |
| | |
| Now that your project is created, you need to add references to the Phidget iOS libraries. This is covered in detail above in the [[#Use our examples |use our examples]] section.
| |
| | |
| After you have linked the Phidget iOS libraries, simply add a reference to phidget22.h in your bridging header file:
| |
| <syntaxhighlight lang="objc">
| |
| #import "phidget22.h"
| |
| </syntaxhighlight>
| |
| | |
| | |
| Success! The project now has access to Phidgets and we are ready to begin coding.
| |
| | |
| ==Write Code==
| |
| {{WriteCode_Intro|Swift}}
| |
| | |
| (Use the C API as a reference when using Swift)
| |
| === Step One: Initialize and Open ===
| |
| You will need to declare your Phidget object in your code. For example, we can declare a digital input object like this:
| |
| <syntaxhighlight lang="swift">
| |
| var ch:PhidgetDigitalInput? = nil
| |
| </syntaxhighlight>
| |
| | |
| | |
| Next, the Phidget object needs to be initialized and opened:
| |
| <syntaxhighlight lang="swift">
| |
| PhidgetDigitalInput_create(&ch)
| |
| Phidget_open(ch)
| |
| </syntaxhighlight>
| |
| | |
| | |
| Although we are not including it on this page, you should include error handling for all Phidget functions. Here is an example of the previous code with error handling:
| |
| <syntaxhighlight lang="swift">
| |
| var res:PhidgetReturnCode = EPHIDGET_OK
| |
| | |
| res = PhidgetDigitalInput_create(&ch)
| |
| if(res != EPHIDGET_OK){
| |
| NSLog("Error")
| |
| }
| |
| | |
| res = Phidget_open(ch)
| |
| if(res != EPHIDGET_OK){
| |
| NSLog("Error")
| |
| }
| |
| Phidget_open(ch)
| |
| </syntaxhighlight>
| |
| | |
| === Step Two: Wait for Attachment (Plugging In) of the Phidget ===
| |
| Simply calling open does not guarantee you can use the Phidget immediately. To use a Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the attach events. Alternatively, we can modify our code so we wait for an attachment:
| |
| | |
| <syntaxhighlight lang="swift">
| |
| PhidgetDigitalInput_create(&ch)
| |
| Phidget_openWaitForAttachment(ch, 5000)
| |
| </syntaxhighlight>
| |
| Waiting for attachment will block indefinitely until a connection is made, or until the timeout value is exceeded.
| |
| | |
| | |
| To use events, we have to modify our code slightly:
| |
| <syntaxhighlight lang="swift">
| |
| PhidgetDigitalInput_create(&ch)
| |
| Phidget_setOnAttachHandler(ch, gotAttach, bridge(self))
| |
| Phidget_open(ch)
| |
| </syntaxhighlight>
| |
| | |
| Next, we have to declare the function that will be called when an attach event is fired - in this case the function ''gotAttach'' will be called.
| |
| | |
| <syntaxhighlight lang="swift">
| |
| let gotAttach: @convention(c)(PhidgetHandle?, UnsafeMutableRawPointer?) -> () = {phid,context in
| |
| DispatchQueue.main.async(execute: {
| |
| let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
| |
| myObject.onAttachHandler()
| |
| })
| |
| }
| |
| </syntaxhighlight>
| |
| | |
| | |
| The bridge function mentioned above is described here:
| |
| <syntaxhighlight lang="swift">
| |
| func bridge<T : AnyObject>(_ obj : T) -> UnsafeMutableRawPointer {
| |
| return Unmanaged.passUnretained(obj).toOpaque()
| |
| }
| |
| </syntaxhighlight>
| |
| | |
| === Step Three: Do Things with the Phidget ===
| |
| We recommend the use of event driven programming when working with Phidgets. In a similar way to handling an attach event as described above, we can also add an event handler for a state change event:
| |
| | |
| <syntaxhighlight lang="swift">
| |
| PhidgetDigitalInput_create(&ch)
| |
| Phidget_setOnAttachHandler(ch, gotAttach, bridge(self))
| |
| PhidgetDigitalInput_setOnStateChangeHandler(ch, gotStateChange, bridge(self))
| |
| Phidget_open(ch)
| |
| </syntaxhighlight>
| |
| | |
| This code will connect a function and an event. In this case, the ''gotStateChange'' function will be called when there has been a change to the devices input. Next, we need to create the ''gotStateChange'' function:
| |
| <syntaxhighlight lang="swift">
| |
| let gotStateChange: @convention(c)(PhidgetDigitalInputHandle?, UnsafeMutableRawPointer?, CInt) -> () = {_,context,cState in
| |
| var state:Int32 = cState
| |
| DispatchQueue.main.async(execute: {
| |
| let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
| |
| myObject.onStateChangeHandler(state)
| |
| })
| |
| }
| |
| </syntaxhighlight>
| |
| | |
| Above, the onStateChangeHandler method is invoked on the main thread. Event data is stored as an Int32.
| |
| | |
| The method onStateChangeHandler is defined as follows:
| |
| | |
| <syntaxhighlight lang="swift">
| |
| func onStateChangeHandler(_ state:Int32){
| |
| if state == 0{
| |
| stateLabel.text = "False"
| |
| }
| |
| else{
| |
| stateLabel.text = "True"
| |
| }
| |
| } | |
| </syntaxhighlight>
| |
| | |
| | |
| If events do not suit your needs, you can also poll the device directly for data using code like this:
| |
| <syntaxhighlight lang="swift">
| |
| var state = 0
| |
| | |
| PhidgetDigitalOutput_getState(ch, &state)
| |
| stateLabel.text = state ? "True" : "False"
| |
| </syntaxhighlight>
| |
| | |
| === Step Four: Close and Delete ===
| |
| At the end of your program, be sure to close your device.
| |
| <syntaxhighlight lang="swift">
| |
| Phidget_close(ch)
| |
| PhidgetDigitalInput_delete(&ch)
| |
| </syntaxhighlight>
| |
| | |
| == Further Reading ==
| |
| | |
| [[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.
| |
| | |
| [[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.
| |
| | |
| [[Using Multiple Phidgets]] - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.
| |
| | |
| [[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.
| |
|
| |
|
| [[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.
| | ===Libraries=== |
|
| |
|
| [[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.
| | {{AllQuickDownloads}} |