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
Current the API simply connects to the single robot which best satisfies the conditions. (Robot type, Robot Name, Signal Strength).
An option for extending this might be to have multiple 'robot specifiers' on the command-line, so that we could require one Dash and one Dot, for example.
eg instead of separate top-level options for --connect-type, --connect-name, it could be multiple --connect arguments, each of which is compound: --connect "num:2 type:dash" --connect "type:dot".
That example would require connection to 2 dash robots and one dot robot.
The text was updated successfully, but these errors were encountered:
@hawflakes,
currently it does accept a list of robot names as part of the 'robot filter'.
there are so many permutations of connection behavior that probably it would be best to provide more callbacks and functions at the API level. eg "OnDiscoveredRobot()" and "RobotManager.connect()" and so on.
How would someone be able to use the present implementation to connect to 2 robots? Is there a quick way of doing it? I would love to demo a short interaction between 2 robots using this lib. :)
Current the API simply connects to the single robot which best satisfies the conditions. (Robot type, Robot Name, Signal Strength).
An option for extending this might be to have multiple 'robot specifiers' on the command-line, so that we could require one Dash and one Dot, for example.
eg instead of separate top-level options for
--connect-type
,--connect-name
, it could be multiple--connect
arguments, each of which is compound:--connect "num:2 type:dash" --connect "type:dot"
.That example would require connection to 2 dash robots and one dot robot.
The text was updated successfully, but these errors were encountered: