Remove 'Update' button

In todays world of experienced users - no longer is there confusion about how to manage buttons / check boxes on pick lists. so 90's. No longer is the off-screen 'Update' button to trick the users into clicking off box is required.

I submit that with the new 'Gui' this small confusion item is no longer necessary and could be removed.

You don't need to hit the "Update" button at all. You can just click the device selector title block (the gray box with "On these notification devices" in your screenshot) and it does the same thing, so I'd suggest trying that instead.

EDIT: The OP was significantly edited after I wrote this reply. For context, it originally requested shrinking the height of the list to make the "Update" button easier to get to, and that is what my reply (and most of the below) refers to.

2 Likes

I think this is a little known fact as to what that Update button even does.

I was helping someone via screen share the other day and every device menu they opened to make a change they would make the change and then click the update button. I did not say anything, since it does not hurt anything to click on it.

Similar to the Save / Enter icons next to input boxes, but those actually don't do anything at all. They just give people a place to click on that gets them out of the dialog box. Then because the clicked somewhere (anywhere) else it does in fact save. Genius actually, whoever came up with the idea of adding those icons.

Thank you for replying. I always know and cringe when I post a feature request I'll get people helping how to avoid needing the feature request. sort of avoids the whole idea of a feature request.

Putting a button on my stove, and then telling my wife, 'You don't need that button' is going to get 10,000 button mashes. Same in gui design. why put the button in the first place?

The update button, as I understood it is legacy due to bugs in past gui. There were situations where the devices and names in the drop down were not up to date relatively, and the update button fixes it. It still does. Today, as I pulled new devices from HA through with name changes the screen was wrong, and the update button fixed it. So I humbly disagree that it isn't useful or valid.
Regarding the 'save' button - omg. thats another ... thing. HTML5 when you push enter or tab, you move field. not so in ajax(?) based web pages as we see in HE. the cursor goes to the page top and you have to reach over grab your mouse and click in the next field. It was something I recall posting about 3 yrs ago and still works the same now.
I realize I'm about to get burned for responding but I've really been trying to be a good citizen around here lately - but its the last day of a new year. I'm going all in I guess.

Edit - I thought I best triple check something - just to be sure before/after I ran my mouth. I admit to running caching tools in my browser to help some dev work I do and other needs. The toggle cache tool I leave on for local hubitat web. I thought maybe it was interacting - but it's not. I ran it both ways, on/off and cleared caches both time - same results.
image
If HE chooses that a feature request is not needed, wanted or extraneous, cool. I'll never see the change and thats that. I accept it. But by not suggested a change or what I might deem an improvement, it will likely never happen. As a community based forum - I like to see others needs and their ideas, I try hard to be open-minded.

1 Like

Nobody is "burning" you for asking, so I would avoid interpreting my or anyone's responses in that way. Rather, it was not clear from your original post if you were aware of this feature, so people are simply pointing out that it exists. That is often the case with feature requests and has nothing to do with you or this one specifically. Perhaps you could let your wife know it exists, too, if she is having trouble. (As with any tool, sometimes you just need to be taught how to use it differently if what you're doing is not working for you. It doesn't hurt to push the button if she wants to, but if it's causing undue strain...)

The "Update" button doesn't do anything that clicking or tapping the box I mentioned above doesn't do. If you see device names change, that can indeed sometimes happen as a result of caching, but clicking or tapping the box to get out and back in will do the same thing (watch the traffic in your browser's Developer Tools network section if you want to verify). There are options in some apps like Groups and Scenes to refresh the list of devices (they use a custom list collected by the app rather than the regular platform device picker, so it's a bit different); while these don't look quite the same, it's possible they are being conflated.

I'm not sure what you mean with the "Save" issues, but creating a new topic with additional details about your concern may be helpful (or updating the title and doing the same here).

Good luck!

1 Like

thank you for your response.

Because back a few years ago, people would get confused about having to click anywhere to proceed with rules they were building, or devices they were selecting in various apps.

People would sit and stare at their screen confused about why the Next or Done button were not there. They would consequently come here and profusely complain about how XYZ app was broken.

The Save button was the fix to force people to click.

2 Likes

I give.

Let me change the title of the post.

Robert already mentioned this, but no one is out to get you. Or prove you wrong. Or make you sorry you made a feature request. Or anything like that.

If you post your thoughts and opinions on a public message board, other people will post their thoughts and opinions in response.

Some of them may not understand what you’re trying to say, some may suggest workarounds to feature requests, and no doubt someone will, at some point, disagree with you.

None of that means you personally are being attacked.

7 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.