You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was going over the spec for my Abstract IO class and comparing with the Raspi IO implementation, and I noticed that queryCapabilities, queryAnalogMapping, and queryPinState are not mentioned in the docs. Are these methods still used and need to be added to the spec, or can they be dropped from Raspi IO?
The text was updated successfully, but these errors were encountered:
I think I answered my own question: these methods exist in firmata.js, but are not used in Johnny-Five, and so I think it's safe to say that we don't need to include these in the IO Plugin protocol. I'm open to counter-arguments though. Primarily, do we care about the IO Plugin spec being 100% compatible with firmata.js or are we okay with it being a subset?
I was going over the spec for my Abstract IO class and comparing with the Raspi IO implementation, and I noticed that
queryCapabilities
,queryAnalogMapping
, andqueryPinState
are not mentioned in the docs. Are these methods still used and need to be added to the spec, or can they be dropped from Raspi IO?The text was updated successfully, but these errors were encountered: