• State Verified Answer
  • Replies 12 replies
  • Subscribers 73 subscribers
  • Views 3501 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 118828
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Master Emulator example differences

Andrew

I am looking at the Master Emulator examples ProximityDemo and HealthThermoDemo. I can use both to connect to one device that I have (Device A). I try to use ProximityDemo to connect to a different device (Device B) but it won't have anything of it. HealthThermoDemo can connect to Device B just fine. I am looking through the code for both and it looks like they do the same things. What is different between the two examples as for how they try to connect?

Note: When ProximityDemo fails, it gets to "masterEmulator.Connect" but then silently fails.

Parents
  • 0

    The HealthThermoDemo uses 2 "BackgroundWorker()" worker functions whereas Proximity app only uses 1. They both have a worker called initMasterEmulatorWorker but HealthThermoDemo has a second worker called backgroundConnectWorker. I have put a break point in that function but it never hits the break point. To summarize, the app the is operates correctly has extra code but the extra code does not get run anyway. I am so confused. :(

Reply
  • 0

    The HealthThermoDemo uses 2 "BackgroundWorker()" worker functions whereas Proximity app only uses 1. They both have a worker called initMasterEmulatorWorker but HealthThermoDemo has a second worker called backgroundConnectWorker. I have put a break point in that function but it never hits the break point. To summarize, the app the is operates correctly has extra code but the extra code does not get run anyway. I am so confused. :(

Children
No Data
Related
Terms of service