getLastFeedback and getOrientation from the same feedback seems inconsistent
update
getState
update
simplifies non-blocking calls
initializeUI
resets the UI to the initial state
getOrientation
3x3 based on IMU. Sometimes IMU is preferrable over AR, so I think it makes sense to add separate methods
get_orientation
getOrientation
getArOrientation
3x3 based on AR
get_position
getPosition
getArPosition
3x1 based on AR
getArPose
4x4 based on AR
(static) findDevice
repeatedly searches until the device is found. Not sure this is necessary, but every matlab demo uses it.
The axis/button states are returned as the normal IO feedback and a struct with the diff states. Off, ToOn etc. enum constants are a pain to deal with in MATLAB and it's more natural to just look at the raw/diff values.
Should setAxisValue be renamed to setAxisPosition ?
HebiMobileIO
wrappermobileIO
wasn't the default namegetLastFeedback
andgetOrientation
from the same feedback seems inconsistentIO
feedback and a struct with the diff states.Off
,ToOn
etc. enum constants are a pain to deal with in MATLAB and it's more natural to just look at the raw/diff values.setAxisValue
be renamed tosetAxisPosition
?