hi vitor,
discoverDevices was put in there as a placeholder when the driver was
written, to be used "later." years passed before anyone even thought
about using the shimmer in master mode, but that eventually came to
pass, so now it's a matter of having solid justification for
implementing the command.
i must say that the stub was not inserted blindly, that exploratory work
was done to see how well the roving networks discovery feature worked
(answer is that it works about as well as any other bluetooth discovery:
hit or miss).
bottom line is that definition of a use case would pre-empt
implementation, and an application layer would also be de rigeur:
how do you use the information after you have it? for starters, how do
you even see it? (host-side app work)
once you know what (slave) devices are available, how do you select what
action to take? how to select among them (host-side? config file on
the shimmer?).
i hope that i answered your question. sorry that the answer contains
more questions!
-steve
On 05/25/2012 10:23 AM, Vitor Pinheiro wrote:
Hi!
How can we use discoverDevices? I don't see any event that occurs after
calling this command. Plus, the command returns nothing. So, hot to use it?
Thanks.
Best regards,
--
V.GilVitorino
_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
