07-27-2012 05:53 PM
One of the apparent changes to version 6 of the SDK, if I'm not mistaken, is that the segmented control must always have an option selected.
In my app, this is not desireable... the app has the user rate a number of items. An analogy would be voting. If you were allowing a user to vote for 4 different things, you wouldn't want to default the vote to one of the people that can be voted for.
Is there a reason for why this was changed?
07-27-2012 11:13 PM
That's a reasonable workaround but I wish the control worked as it did before -- to allow no selection.
07-27-2012 11:16 PM
Actually, that doesn't work because the control only allows up to four options and I need all four options for valid choices, thus I can't add a "" option to represent no selection.
07-27-2012 11:59 PM
You could implement your own custom controls.
Not sure what exactly you're making, but you may want to think about simplifying the amount of options that your end user needs to select on any given screen. It can be very easy to quickly overwhelm someone with lots of options.
07-28-2012 07:22 AM
Yes, that's a good point and I've also considered that. For example, Android has a rating control where you click on stars. The downside is that takes more time and then you don't get the highly polished widget produced by RIM with nice fades etc.
07-30-2012 04:02 PM
Generally, SegmentationControl gives me the impression that each option leads to an existing concrete result of some sort; therefore it makes no sense to me to have one that does not contain a 'current' selection.
Although the UI would be different, RadioGroups come to mind when I think of singular selection with the possibility of null values. Depending on your UI design, this could work very well.
07-30-2012 09:42 PM - edited 07-30-2012 09:43 PM
I suppose I'm using the segmented control as more of a "rating control", or a "voting control" and so my desire for there to be a non-selected state follows from that. I think I agree with your premise if you're using it entirely within the narrow scope you suggest.
That said, it's not clear to me that limiting the control in this way is wise because you then exclude the control from being used as a rating control. Hard to say. Android has a rating control, BB10 does not. It seems tempting to relax a constraint of the segmented control as was the case in release 4 of the SDK to allow the control to be used in the broader context.
07-31-2012 09:54 AM - edited 07-31-2012 09:55 AM
Thanks for your input;
Another option would be to implement a custom control which would take some effort. I agree that such a Rating control would be very useful - I recommend placing a feature request on our issue tracker for such a new control, or for adjustments to the existing SegmentationControl (as it used to function in the past). This risks becoming a very popular use-case and request; developers would definitely benefit from this moving forward.
Issue tracker: https://www.blackberry.com/jira/secure/Dashboard.j
08-01-2012 09:03 PM