radiobuttons instead of ImgageButton. Then the state is handled
automatically (using state checked as well as pressed).
On 30 Juni, 20:21, Neilz <neilhorn...@gmail.com> wrote:
> I have this situation quite often, and simply stick to three
> ImageButtons. It means you need pressed and static states for each
> button, controlled by an xml selector as the drawable, and of course
> you have to manage the states yourself, i.e. set the pressed button as
> 'pressed' and the other two as static.
>
> If you go down this route, manage the states in a runnable which fires
> about 100millis after the press, so that the default button 'up'
> action doesn't undo your work.
>
> On Jun 30, 6:07 pm, nadam <a...@anyro.se> wrote:
>
>
>
>
>
>
>
> > Is there any obvious Android alternative to iPhone toggles like this
> > (DHCP/BootP/Static)?http://www.coderetard.com/wp-content/uploads/2008/06/iphone_ip.jpg
>
> > Need it on the top of a listview to let the user choose how the list
> > is sorted. Placing three radiobuttons side by side doesn't look good
> > and possibly would be too wide on small screens. Have tried Android's
> > toggle buttons too, but hope there is something better around.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment