You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being able to handle ontap events, and possibly even show a tooltip can be a great way to give context and meaning to progress.
In my case, I want the user to move for a set time each hour (eg walk 10 mins each hour between 9-17)
Lets say a user doesnt finish his step from 11:00-12:00 and wants context, it would be great if I could display he walked for only 5 minutes during this step when he taps the step.
Any ideas on how this can be achieved?
I've looked a little bit at your code, and gesturedetector. I think this might get quite complex, but perhaps there's some tricks I dont know of yet.
Other enhancement could be adding a ontap for a circle, whilst also allowing ontaps for nested circles.
Although less detailed than a step, this could be a nice and simpler start.
The text was updated successfully, but these errors were encountered:
The main problem with the onTap gesture on the CircularProgressIndicator when I introduced it was that I use a CustomPainter to draw the circular indicator, so it was more difficult to correctly detect the tap in the steps.
Lately, I found this package touchable. It allows adding custom behaviors on tap on a CustomPainter. I may consider adding it. Basically, I would add an onTap attribute also to CircularProgressIndicator exactly like a normal StepProgressIndicator.
Hi again,
Being able to handle ontap events, and possibly even show a tooltip can be a great way to give context and meaning to progress.
In my case, I want the user to move for a set time each hour (eg walk 10 mins each hour between 9-17)
Lets say a user doesnt finish his step from 11:00-12:00 and wants context, it would be great if I could display he walked for only 5 minutes during this step when he taps the step.
Any ideas on how this can be achieved?
I've looked a little bit at your code, and gesturedetector. I think this might get quite complex, but perhaps there's some tricks I dont know of yet.
Other enhancement could be adding a ontap for a circle, whilst also allowing ontaps for nested circles.
Although less detailed than a step, this could be a nice and simpler start.
The text was updated successfully, but these errors were encountered: