Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Should toggle button show its current state or the state to which it'll change? (2010)

ux.stackexchange.com

Post reply on HN
Print view View original

211–220 of 303 posts

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#211

Post by continuational »

Sindisil wrote: post #34
Waterluvian wrote: post #23

Earlier quoted context omitted.

> A light also has the advantage of being a skeuomorph Unless you’re my TV and it’s completely backwards for some reason.

The standby light on a TV in on for standby and off when viewing because a) it could be distracting and annoying for the extra LED to be shining while viewing in a darkened room, and b) the "on" state should be pretty obvious because of the stuff on the screen.

And also, putting the TV in standby mode is an offense punishable by a denial of darkness attack.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#212

Post by crazygringo »

IggleSniggle wrote: post #182
crazygringo wrote: post #48

Earlier quoted context omitted.

> Give me labels. If labels don't fit your motif then get better designers. That's unhelpful and unreasonable, particularly on mobile. There's no room on Spotify for labels behind every button, for instance. Not if you want room to show the cover art, which I do. It's not a question about "better designers" -- space constraints are real, and sometimes you really need things available at a single tap. I don't want shu…

I just opened Spotify on my iPhone mini, just to check, and I really have to disagree. Spotify has TONS of wasted space. Even when you do want to pull up the "extra" menus (which is frequent for me, since it seems like that's the only place to get to the album for a given song), they practically throw the space away. The hamburger menu can only fit two items on its list of 10, because they waste so much space. I'm so…

> Spotify has TONS of wasted space.

Not on my iPhone SE screen.

I wouldn't want the buttons or even menu items to be any closer together. It's not about information density, it's about tap areas.

And I'm tapping the screen on the go, on a bumpy bus, being jostled in the subway.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#213

Post by adamwk »

AlienRobot wrote: post #203
bee_rider wrote: post #189

Earlier quoted context omitted.

Sounds kind of hard to use on mobile, which is indisputably a popular set of platforms. No need to throw the baby out with the bathwater. Big (resizable) UI elements with poke-ability are fine. Auto-saving can be great depending on the application. Let’s just ditch the false simplicity and flatness.

Every single time I'm on desktop and I see a GUI that sucks, I know it's mobile's fault. Why this button so big? Mobile. Why spacing? Mobile. Why this list of 6 clickable items with one line of text each takes up my whole screen's vertical space? Mobile. Why no more status bars and tooltips? Because you can't hover on mobile. Why is the filter of this table below the table instead of above the table's headers? Becaus…

Screen size isn’t the problem for mobile, it’s tap targets

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#214

Post by avgcorrection »

Not directly related but Bitbucket cloud has made some recent update where they started prioritizing reviewers over submitters in pull requests. One change is that you by default get the “I’m reviewing” filter turned on by default. Which I have to turn off most of the time. Anyway, sometimes I try to turn it off but then it is toggled (it was off). What’s going on? Well, the normal interface is that it’s a combobox where no-text means no filter—that’s where the I’m Reviewing by-default resides. But on a slightly different pull request view—which looks almost the same—the UI element is the same kind of thing... except here the combobox gets a black background when toggled! And the default is to show some option like I’m Reviewing but on a white background, which means not-toggled…

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#215

Post by csydas »

beezlebroxxxxxx wrote: post #206
csydas wrote: post #200

Earlier quoted context omitted.

I don't mean to just blanket shit on Teams, but Teams is just a confusing mess of UI choices and UX design that makes no sense even within the context of using Teams. The meeting icons are of course pretty awful as you cited, but it's even more things for me [0]: - When joining a Teams call, the toggle for video gets "selected" so that pressing Return or spacebar (I think one or both) will toggle the video on -- noti…

One thing absolutely bizarre with Teams is that if you copy and paste the contents of a message most of the time it will paste the contents as plain text with a weird timestamped wrapper including the senders name. That makes passing a filepath or any text super annoying through Teams, most of all because it's a seemingly random behaviour --- sometimes it does it and sometimes it doesn't.

Ah I know of this one and yes it's very annoying. But I can explain the behavior for you, though it won't be any less random-seeming in my experience.

Depending on where you stop your selection with the cursor, Teams will think you either only have text selected, or you've selected the message itself. The latter is what adds the message data to your clipboard, and the border between text and message selection is impossible to tell. On MacOS I can _barely_ see some text highlighting when I grab the message, but it's not always clear.

Edit: additional complaint

Teams is bad with text in general. It inserts so many random new lines and hidden characters for cosmetic purposes only, and unless you've dealt with the issue before, you have no way of knowing why the powershell one-liner you copied from teams has a bunch of ????????? at random places like code blocks.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#217

Post by watwut »

mywittyname wrote: post #163
fckgw wrote: post #154

Earlier quoted context omitted.

You're looking for literally any Hyundai, Kia, Toyota, Honda, Chevy or Mazda sedan. Hope this helps.

Automatic Emergency Braking and adaptive cruise are difficult features to avoid. The IIHS dings vehicle safety ratings if they do not have AEB. Because of that, even entry level vehicles like the Elantra have AEB. Almost every manufacture has committed AEB on their entire lineup.

He asked for "no batshit insane" breaking system. Sane systems that engage only when it is truly last moment rather then overeagerly or randomly exists. My seat basically never breaks despite having the feature - because itnis setup for actual emergency.

Plus, you can turn it off.

You can always turn off lane control too.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#218

Post by ambigious7777 »

the_other wrote: post #51
derekp7 wrote: post #6

This has been really frustrating to me lately with Microsoft Teams. If I'm in their app, the mute button is a microphone with a line through it (if mute is activated, i.e. if the mic is off). And the icon changes to a microphone without the slash over it to indicate that you are no longer muted. Makes sense. But if I join using the phone app on my phone, the same microphone with a line through it (that means you are…

There's a pretty interesting (to me) aspect of the mic indicator/controller problem: without direct visual feedback, you can't tell what mode your mic is in until _other people_ respond, or don't. It's a very laggy tool in terms of feedback even when it's "on". In fact, you often need to test it two or three times to be sure, because your fellow meeting members might have frozen, might just be thinking before they re…

I think the solution to this problem would be to have a indicator on your profile that say is green when you can talk, but red or gone when you can't.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#219

Post by sumtechguy »

kqr wrote: post #89
sponaugle wrote: post #79

I have some old NASA push button switches that have two bulbs in them. When the switch is off both lights are off, when you click the switch the yellow bulb comes on and lights up the switch, and when the device you turned on actually turns on a green light turns on ( and the yellow turns off ). The idea is you push the button and the yellow state is the confirmation that you toggled the switch, but the green is the…

This is a good one, and also what airplanes do[1]. These problems are solved by people who care a lot about usability, but computer people are slow to pick up this sort of stuff from other fields. Labels outside the switch also work.[2] [1]: https://my737ng.com/wp-content/uploads/2014/08/cp_mcp_header... [2]: https://i.pinimg.com/originals/2c/37/0a/2c370a3f4018cfa9c3ef...

The real pain is this WAS a solved problem in computers too. Almost all of the GUI OS's had a style guide. Usually 2-3 pages at most (usually smaller) and fairly easy to follow. Then everyone went bonkers and wanted to make their own. Then dump that all into one desktop and good luck... Every app is special.
Post reply on HN