Please help make UI design decision
-
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
There have been many takes on this particular subject in the design community over the years. The consensus seems to be, at the moment, if a user is never going to be able to use that field, you should hide it. If it can be used in certain circumstances, you should disable it.
-
Behzad Sedighzadeh wrote:
What, you, the community think is a better option?
Don't worry about such silly nonsense. Be considerate. What you should be doing is Helping Dave[^]
That's just trolling now.
-
That's just trolling now.
-
That's just trolling now.
-
That's just trolling now.
-
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
I prefer 1. It provides more information.
-
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
I would prefer option 1. I would be more concerned about having the checkbox in the Settings form and the item being enabled/disabled on a tab in another form. What is the user going to think when they are in the Alarms tab and see a disabled section? Probably 'why is this disabled, I want to edit it.' Try not to make the user navigate away to the Settings form. Does it make sense to have the checkbox (or a duplicate) on the Alarms tab? At the least you need some way to indicate to the user why they can not access those controls. Users do not read manuals. Make things that the user is likely to do easy to do.
-
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
I would go for option 1.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
As long as the checkbox is on the Alarms Tab so: The Alarms Tab is always enabled The checkbox on that tab is always enabled When the checkbox is clicked, the other controls on the Alarms tab are enabled
-
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
If the Alarms tab is in the Settings form or its form is visible while viewing the Settings form I would choose Option 1. Otherwise, it doesn't really matter unless being able to see the option in the Alarms tab would help the user understand what options might be available, in which case Option 1 is again preferred.
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes) -
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms": Option 1: which was visible but disabled, gets enabled. Option 2: which was hidden, added to the TabControl again. In terms of UI design decision, which method you prefer? Personally, I like option 1. What, you, the community think is a better option?
Behzad
I would disable the tab and display an informational icon with a tooltip that explains why the option isn't available, and hide the icon when the tab is enabled. #DontLeaveYourUsersGuessing :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com