-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binding does not respect list of service ids in DiscoverServices, and instead tells windows to discover all (slow).) #19
Comments
AFAIK the only available method is GetGattServicesForUuidAsync which would only request a single service. So to implement this we'd have two cases:
If anyone wants to implement this I can provide further guidance. |
It's looking more and more like I am going to need to do this. The same deficiency is in noble_uwp. I could knock this out in JS, but I am going to be bumbling around in C. Ill give it a shot. Any web links on debugging node c modules, and tracking multiple async events are appreciated. |
I am assuming we want to hit peripheral_winrt/getService instead of going directly to the device? getService is a callback pattern. Assuming we want to get each service in series, maybe I could do a recursive callback situation? |
I get a ton of build errors before making any changes. Can I get some help on how to set my build system to ignore these things? I am assuming I am using tools that are too new or something like that?
|
Nevermind....adding |
This is as far as I have been able to get. It works with one service uuid, but for more than one it just gets all. noble-winrt doesnt seem to have any foundation for emitting an error instead of a list of discovered serviceids.
|
It also appears that device.GetGattServicesAsync does not populate the internal cache of services upon completion? |
This function simply requests all services from windows, and then filters the list, instead of requesting specific services from windows. For some devices with many services, this is slower than necessary.
The text was updated successfully, but these errors were encountered: