Hi There, I am developing a PC app that will utilize a couple different aspects of the IOIO. In particular, I am starting with the TWI (I2C) and GPIOs. I have implemented a nice TWI class that is also a IOIOLooperProvider, and it works well. Now that I am starting to implement my GPIO stuff, I find myself polluting my TWI class with GPIO code. Looking more into the API, I thought of two approaches:
1) Have a single, more multi-purpose IOIOLooper that creates the TWI interface and hands it off to the TWI class, and also manages the GPIO stuff. 2) Create two separate IOIOLoopers that each do their own thing, and somehow get two of them up and running over one USB connection to the board. I know I can implement #1, but this makes a pretty specific IOIOLooper that does everything, while #2 seems like a more flexible and generic approach, but I don't know if this is possible or even the intent of the API. What is the intended way to do this? A brief look at the code seems to indicate it might be possible, but I can't tell yet if multiple IOIOLoopers can share the same connection or if they are intended to be used one per connection. Thanks in advance for any advice, Mark. -- 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/d/optout.
