I'm trying to wire up multiple combo buttons in the same corner of the screen. The first one triggers the 'onactivate' method properly.
The 'onactivate' method hides one <svg> node and shows another <svg> node that contains a second combo button in the same corner as the first. It shows fine and even seems to do the touch animation. The issue is that the second combo button doesn't get it's 'onactivate' method triggered. No console errors are generated.
Suggestions?
Answered! Go to the Best Answer.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
The `onactivate` event seems to have some issues in the current beta, try using the `onclick` event.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
For what it's worth. The issue with the 'onactivate' seems to bug out when it is contained within an <svg> node that is hidden.
I had another combo button elsewhere that was working just fine until I hid and showed it's parent <svg> node; then the combo button stopped working, as I noted in the first post.
Best AnswerI still have problems with the onactivate method - should it work proberly now?
onclick on a combobutton works - onactivate doesn't
Actually I want to start the action which I start with onclick with a combobutton bottomright also with the hardbutton on the right down side.
Capitano
Best AnswerI recognize that this is about a year and a half old, but I am still experiencing this problem. Was there ever a fix or is Fitbit leaving us hanging like they did with Spotify support? Really getting frustrated with them right now.
Best Answer