11-07-2017 18:41
11-07-2017 18:41
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.
11-08-2017 03:22
11-08-2017 03:22
The `onactivate` event seems to have some issues in the current beta, try using the `onclick` event.
11-08-2017 03:22
11-08-2017 03:22
The `onactivate` event seems to have some issues in the current beta, try using the `onclick` event.
11-08-2017 04:15
11-08-2017 04:15
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.
12-30-2017 03:56
12-30-2017 03:56
I 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
04-18-2019 21:39 - edited 04-18-2019 21:40
04-18-2019 21:39 - edited 04-18-2019 21:40
I 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.