What you want to do falls outside the scope of IOIOActivity. So what you basically want to do is look at how IOIOActivity is implemented (calling methods of IOIOAndroidApplicationHelper at different times) and modify it to suit your needs.
On Fri, Feb 28, 2014 at 11:19 PM, Chiong Ching Lai <[email protected]>wrote: > Hi there, > > What I want: > I have a project that consist of 2 Activities, the first one extends > IOIOActivity and is showing the main screen and responsible for detecting > and creating IOIO connection (through a Looper extending BaseIOIOLooper). > When IOIO connection is established, a button will be enabled. Clicking > this button will start a second Activity which extends FragmentActivity. > > The second Activity will be handling the control of the IOIO peripheral > (DIgitalIO, I2C, etc). When a disconnection is detected, the second > Activity should be destroyed and the first Activity should be shown. > > What actually happens: > When the second Activity is started, it seems that the IOIO object as > created by the Looper class will be disconnected and the disconnected() > method is called. > > Can anyone please help? Attached is the code and layout for the first > Activity and the AndroidManifest. > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/groups/opt_out.
