(Swift 2) PC/SC Async Wait for Smart Card Status Change (Inserted, Removed from Reader, etc.)

See more SCard Examples

Demonstrates how to start an asynchronous Chilkat task to wait for a status change, such as for a smart card to be inserted into a reader, or removed from a reader. After starting the background task, the code loops to check on the status of your task.

Note: Instead of writing a loop to wait for the status change, your application might periodically check the task status via a timer event or something similar. The purpose of this example is to show (1) how to start the async task, and (2) how to periodically check the status of the task.

Note: This functionality was introduced in Chilkat v9.5.0.87.

Chilkat Downloads for the Swift Programming Language MAC OS X (Cocoa) Objective-C/Swift Libs iOS Objective-C/Swift Libs

func chilkatTest() {
    // This example requires the Chilkat API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    let scard = CkoSCard()

    // First establish a context to the PC/SC Resource Manager
    var success: Bool = scard.EstablishContext("user")
    if success == false {
        print("\(scard.LastErrorText)")
        return
    }

    // Get the list of all readers.
    let stReaders = CkoStringTable()
    success = scard.ListReaders(stReaders)
    if success == false {
        print("\(scard.LastErrorText)")
        return
    }

    // Create a Chilkat task to wait for a max of 1 hour (3600 seconds, or 3600000 milliseconds) for any smart card reader status change.
    let json = CkoJsonObject()
    var task: CkoTask? = scard.GetStatusChangeAsync(3600000, stReaderNames: stReaders, json: json)
    if scard.LastMethodSuccess == false {
        print("\(scard.LastErrorText)")
        return
    }

    // Start the task in a background thread.
    success = task!.Run()
    if !success {
        print("\(task!.LastErrorText)")
    }

    // Loop until the task is finished, which happens when any reader's status changes.
    // Instead of looping here, your application could periodically check on the task status in some other way,
    // such as in a periodic timer event..
    while task!.Finished != true {

        // Sleep 100 ms.  
        task!.SleepMs(100)
    }

    // When we call GetStatusChangeAsync, what's really happening is that GetStatusChange is being called in a background thread.
    // It returns a boolean (success/failure).  Therefore, we call task.GetResultBool to get the boolean returned by GetStatusChange
    // in the background thread.
    success = task!.GetResultBool()
    if success == false {
        // The call to GetStatusChange in the background thread failed.  Let's find out why by getting the LastErrorText
        // for the background synchronous call.
        print("\(task!.ResultErrorText)")
    }

    task = nil

    // If the background call to GetStatusChange succeeded, then the result was placed in the last arg,
    // which was our variable named "json".
    if success == false {
        return
    }

    // Let's see what happened...
    json.EmitCompact = false
    print("\(json.Emit())")
    print(" ")

    // See the Wait for Smart Card Insertion/Removal Example for details about parsing the returned JSON.

    // Applications should always release the context when finished.
    success = scard.ReleaseContext()
    if success == false {
        print("\(scard.LastErrorText)")
    }

    // Note: It may be necessary to call FinalizeThreadPool in some programming environments just before your program exits.
    // (Not after every async function call, but only before program exit.)
    // See Call FinalizeThreadPool before program exit

}