Skip to content
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

Send "ggkNofifyUpdatedCharacteristic" while still operating on a different Characteristic. #18

Open
junmilreyso opened this issue Feb 27, 2019 · 0 comments

Comments

@junmilreyso
Copy link

How can I make the ff. perform in the correct order within characteristicA's dataSetter?

  1. Write on characteristicA
  2. Notify characteristicB w/ new value "1"
  3. Perform some internal logic in standalone
  4. Notify characteristicB w/ new value "0"

Currently I get the ff. order for the values I receive on characteristicB:

  1. Write on characteristicA
  2. Perform some internal logic in standalone
  3. Notify characteristicB w/ new value "1"
  4. Notify characteristicB w/ new value "0"

Initial investigation shows that "ggkNofifyUpdatedCharacteristic" adds the notification entries into a queue and only pops the items in the queue after I perform the internal logic and I exit the dataSetter function. Is it possible to make the first scenario work in GGK?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant