[Bug 165134] desktop context menu: disable menu entries, do not remove them (HIG violation)

Maciej Pilichowski bluedzins at wp.pl
Sat Jun 28 13:53:54 CEST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=165134         
bluedzins wp pl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|DUPLICATE                   |



------- Additional Comments From bluedzins wp pl  2008-06-28 13:53 -------
> >  Just like the context menu between right-click at a tar.gz (has the
> > items "Open with Ark" and "Extract...") and a directory 

The context is object, not situation! You should get the same context menu (items list) when you click on tar.gz in read-only mode and when write is possible. The same object, the same context menu.
The same context menu for directory in read-only mode and write mode.

Directory is another object so it is ok, the context menu changed (comparing to tar.gz).

If you read explanation (and arguments) given by William you would notice the mentioned benefits. 

Currently both context menu are very similar, so similar then they are not really different context menu (as for .tar.gz vs. directory) but the same, with some hidden features. The point is, that disabling them instead of hiding gives user extra information, user sees the function is there, that nothing is missing.

And the bottom line is, that this behaviour violates HIG, quote:
"
Menu items should not be added or removed during runtime. Disable or enable them instead.
"

I didn't wrote this, I just quote this, and I believe all KDE apps should follow HIG, do you agree with that?

( btw. reopening, since it is not a duplicate, those reports are related to context menu but have something different in mind ).

> See http://en.wikipedia.org/wiki/Context_menu 

Good link. Look at the first image at that page. Yes, this is correct example of context menu, unavailable option is _disabled_ not _removed_.


( with IRC there is problem of synchronizing people and thus I avoid this, but if you would really prefer this, please let me know about the details )


More information about the Panel-devel mailing list