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
* Just saw this might be a duplicate, sorry - newbie failure*
Hi,
just checked out this nice piece of code (thanks !) and ran into an issue.
I rely on the ability to deselect all segments in the segemented control.
For UISegmentedControl this is possible by setting the selectedSegmentIndex to -1.
Thanks for the report, this is probably related to the other issue about selectedIndex. The original design was to always have an index selected which is the reason for the NSParameterAsset not allowing anything outside of the index range to be set. However, several users have reported an issue with deselecting all indexes so hopefully I can get around to implementing this fix this weekend.
* Just saw this might be a duplicate, sorry - newbie failure*
Hi,
just checked out this nice piece of code (thanks !) and ran into an issue.
I rely on the ability to deselect all segments in the segemented control.
For UISegmentedControl this is possible by setting the selectedSegmentIndex to -1.
URBSegmentedControl has some checks in
that do not allow -1 as a value.
Tried the following change as a quick and dirty hack:
...
From what I see this does the trick, but I don´t know your code in detail yet.
Maybe you can check and adjust this.
Cheers,
Oggerschummer
The text was updated successfully, but these errors were encountered: