281–290 of 303 posts
Any Tesla owner can relate to this, given the wide variety (read: no consistency, no standards) of toggle buttons the car's UI utilizes. For one, the HVAC. One button, showing temperature, which upon touched the system will react differently to depending on how you touch it and for how long. Touch it briefly, you get a little popup. Touch it slightly longer, and (hopefully, not guaranteed though) you get a bigger pan…
Earlier quoted context omitted.
this is backwards from the perspective of digital logic circuits physical light switches toggle between closed-circuit and open-circuit, not high and low voltage levels. 'on', where current can flow, is a closed circuit; 'off' is an open circuit in digital logic, when there is a correspondence between closed/open and high/low, the correspondence is virtually always that closed is low and high is open. for example: tt…
Oh, of course that must be what closed circuit meant. For some reason I just thought “looks like the switches are little doors, like in a floor plan, and they are all closed now” and I never examined it.
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…
A chunk of my early career was writing GUI software to control and display state of remote hardware, and I quickly learned to banish any "stateful" UI elements - those that retained their own state and changed behavior based on that state, like toggles, switches, check boxes, radio boxes, etc - because it wasn't uncommon for the interface and hardware state to get out of sync. What I ended up settling on to replace t…
> I did experimented with displaying both the commanded state and received state in various ways
Did you try keeping the commanded button in the pressed state until the next state update? I feel like that should be fairly intuitive to most people, and it'd still allow you to give a different command while the state hasn't updated yet.
Any Tesla owner can relate to this, given the wide variety (read: no consistency, no standards) of toggle buttons the car's UI utilizes. For one, the HVAC. One button, showing temperature, which upon touched the system will react differently to depending on how you touch it and for how long. Touch it briefly, you get a little popup. Touch it slightly longer, and (hopefully, not guaranteed though) you get a bigger pan…
1. Look at it
2. If it's slightly transparent and I want to turn it on, I click it (I don't hold for a second or 2 or 10, I just click it normally) and it turns on
3. Click it again to get the full controls
4. Slide down to close the full controls
5. Click the button again to open the full controls, and click the off button to turn it off.
Then I click and slide to the right or left to increase or decrease the temperature.
Seems pretty intuitive to me.
I'm gonna try clicking and holding next time I drive to turn it off, seems really useful.
Earlier quoted context omitted.
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.
On the Apple side, things look a lot better. They were able to keep most apps using the native UI.
Earlier quoted context omitted.
It also parses certain C++ and Fortran syntax as smileys...
It had ( had !) a multi-line code block option. Now it still does, but only in the desktop app, not in the browser. I'm sure they need some native platform APIs to enable entering multi-line code blocks.
Earlier quoted context omitted.
It had ( had !) a multi-line code block option. Now it still does, but only in the desktop app, not in the browser. I'm sure they need some native platform APIs to enable entering multi-line code blocks.
Isn't this the company that makes VSCode as well though? Why not pillage some of that code for ... code in messages?
Earlier quoted context omitted.
> computer people are slow to pick up this sort of stuff from other fields Because computer people aren't optimizing for functionality, intuitiveness, or really any sort of UX. They're optimizing for some idea of "beauty" and whatever is trendy.
And you don’t die if your mute switch is in the wrong position at the wrong time.
Any Tesla owner can relate to this, given the wide variety (read: no consistency, no standards) of toggle buttons the car's UI utilizes. For one, the HVAC. One button, showing temperature, which upon touched the system will react differently to depending on how you touch it and for how long. Touch it briefly, you get a little popup. Touch it slightly longer, and (hopefully, not guaranteed though) you get a bigger pan…
Tesla's mobile app features inconsistent toggles right next to each other! - A closed padlock means the doors are locked. Tapping it unlocks the doors. - The word "Open" on the trunk means the trunk is closed. Tapping it opens the trunk.
Also click-and-hold with or without haptics is not obvious. I was stabbing at the Tesla screen to activate defrost in a snow storm. I had to call the owner to figure out why it would not activate. I really like the 3 but you cant just hop in and go without some prep.
Earlier quoted context omitted.
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.