Re: setHidden: on MacOS 10.2
Re: setHidden: on MacOS 10.2
- Subject: Re: setHidden: on MacOS 10.2
- From: Jeremy Dronfield <email@hidden>
- Date: Fri, 30 Apr 2004 10:27:59 +0100
On 30 Apr 2004, at 12:03 am, Public Look wrote:
Best of all, don't hide interactive controls! Why not just disable
the control that is not applicable.
Whilst this is probably true in most cases, it is a gross
over-generalisation. It depends on the UI and the context in which
controls are hidden. For example, I have an application which features
a set of table views in its main window which are used for managing
files. The user can choose to hide the tables; when they're hidden, I
also hide a search field which is above them in the window. The search
field is useless without the tables, but is not part of the same
subview. Therefore, it has to be explicitly hidden. The reason I hide
it rather than disable it is this: the window resizes when the tables
are removed, and removing the search field balances up the changed
aesthetics. I think it's obvious to the user that the application is in
"writing" mode rather than "search-and-browse" mode, even though the
search field isn't an integral part of the tables' subview. In short,
the approach works, and works well; a perfectly valid situation in
which to -setHidden: an interactive control.
is evil <snip> it is probably evil. <snip> for something evil ?
You're perfectly entitled to follow your own path to righteousness, but
the rest of us are not necessarily damned just because you say so.
See my rants on this topic in the archives.
Why on earth would we want to do that?
Regards,
-Jeremy
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.