The pins don't open themselves, so you can simply store every pin you open in an array / map / etc. They also don't set their own output, so once again, you can store this state yourself. For input pins, read() will tell you the value.
This behavior is one purpose - when designing the API I've tried to not expose functionality that the client can implement themselves, unless there's a good reason to do so. If you don't like this behavior, you can easily add thin wrappers around the interfaces that would store any additional state. On Sat, Mar 1, 2014 at 11:04 AM, doron atuar <[email protected]> wrote: > Hi, > > is there a way to to print the pins state ? > like which one is open and which has a LOW/HIGH logic level? > > thanks, > Doron > > -- > 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.
