05-15-2012 04:21 PM
When debugging a project, I realized that the SegmentedControl fires only the Event.CHANGE when the user taps on the UI element and not when the user ends dragging the tab.
It feels like a bug to me, but I'd like to confirm with you people if there is something I am missing.
I tried on desktop and on the Playbook. I develop with FDT5.5.
Solved! Go to Solution.
05-16-2012 11:20 AM
The SegmentedControl was designed on purpose to be tap only. Think of it more like a row of buttons, like the nav bar of a website.
05-16-2012 12:02 PM
Thanks for replying quickly!
I understand the design choice, however I believe that there may be cases where the user will see that you can drag the bar and not understand why no trigger happens when they release their finger on a new option.
05-16-2012 01:47 PM
This is standard functionality across all mobile devices. Personally I think the choice was made not to drag because your finger obfuscates the options.
If you would like drag functionality you can always use a slider control and have it snap to specific options. If you present the options above the slider I think it would work well. You'll have to write the snap to code yourself however.
I do agree that the look of the component makes it appear as if the toggle can be dragged. Something like distinct lines in between options might be a good idea. I'll talk to the SDK team.
05-16-2012 01:52 PM
05-16-2012 02:05 PM
This component is not meant to be dragged.
The only event fired is the change event.