New Processing example (filter by connection type) #45

Merged
merged 4 commits into from Dec 30, 2012

Conversation

2 participants
@SableRaf
Contributor

SableRaf commented Dec 25, 2012

Filter connected controllers by connection type (USB or Bluetooth) and show their battery level, MAC adress and connection type.

SableRaf added some commits Dec 22, 2012

Get battery levels for all controllers connected
Also, filtering duplicate controllers by their id (MAC address)
New Processing example (connection type)
Filter connected controllers by connection type (USB or Bluetooth) and
show their battery level, MAC adress and connection type.
Unlock exposure function
Added function to be called at startup in order to remove previous
exposure lock.
@SableRaf

This comment has been minimized.

Show comment Hide comment
@SableRaf

SableRaf Dec 25, 2012

Contributor

About the unlock exposure for startup, I'm not completely sure how to do it but I added this as a suggested solution.

Contributor

SableRaf commented Dec 25, 2012

About the unlock exposure for startup, I'm not completely sure how to do it but I added this as a suggested solution.

New processing examples (doc)
Port of the usage examples from the doc of the API.

thp added a commit that referenced this pull request Dec 30, 2012

Merge pull request #45 from SableRaf/master
New Processing example (filter by connection type)

@thp thp merged commit 3f02e30 into thp:master Dec 30, 2012

@thp

This comment has been minimized.

Show comment Hide comment
@thp

thp Dec 30, 2012

Owner

Merged, thanks. You probably also want to call your camera_control_initialize function somewhere, right?

Owner

thp commented Dec 30, 2012

Merged, thanks. You probably also want to call your camera_control_initialize function somewhere, right?

@SableRaf

This comment has been minimized.

Show comment Hide comment
@SableRaf

SableRaf Dec 31, 2012

Contributor

Affirmative. It should get called before the calibration starts. I would
have done it myself but I was confused as where to put it. Thanks for the
merge.

Contributor

SableRaf commented Dec 31, 2012

Affirmative. It should get called before the calibration starts. I would
have done it myself but I was confused as where to put it. Thanks for the
merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment