[plasmashell] [Bug 509471] Unavailable items on the login screen are disabled rather than hidden

[Sune Vuorela]

https://bugs.kde.org/show_bug.cgi?id=509471

Sune Vuorela <kde at pusling.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kde at pusling.com

--- Comment #4 from Sune Vuorela <kde at pusling.com> ---
(In reply to Nate Graham from comment #3) 
> The question is whether we want to continue to disable these buttons, or
> hide them instead.

My Opinion (which of course always is the correct one) is that if the user
might be looking for the feature/button/.. it should be there but disabled
(maybe a hover text to inform the user of 'why'). Also if it is a thing that
the user might want to do in a common case, make it disabled, maybe with a
hover text to explain how.

If it is unlikely the user want to do it and need to do it, it is just visual
clutter.
It can also be conditional.

That can lead to a bit complex decision trees of course:

If(feature-B-is-selected) {
  if (frobnizzer-found) {
  button->onClicked(activateFrobnizzer);
  }  else {
  button->setDisabled(true);
  button->setHoverText("Frobnizzer not found. Please get it available");
  }
} else {
  // Frobnizzer only makes sense if feature B is active
  button->hide();
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.