When I first wrote HelloIOIOPower, it was impossible for an app extending AbstractIOIOActivity to respond to a disconnect. This has now changed, so HelloIOIOPower doesn't do anything that cannot be done with AbstractIOIOActivity.
However, the point being made remains valid:
You don't have to use AbstractIOIOActivity (and stick to the setup-loop-loop-loop-disconnect paradigm, to starting and stopping the connection in response to activity pause / resume, or to a single IOIO thread) for writing IOIO applications. You can explicitly create the IOIO object, and call waitForConnect() / disconnect() whenever you want, and do whatever you want with the IOIO instance, even from multiple threads at the same time (the API is completely thread-safe).
--
You received this message because you are subscribed to the Google Groups "ioio-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/jC6GKPJs3HQJ.
To post to this group, send email to ioio-...@googlegroups.com.
To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ioio-users?hl=en.
To unsubscribe from this group and stop receiving emails from it, send an email to ioio-users+...@googlegroups.com.
To post to this group, send email to ioio-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.