Missing inactive and disabled states on some controls
Missing inactive and disabled states on some controls
- Subject: Missing inactive and disabled states on some controls
- From: Brock Brandenberg <email@hidden>
- Date: Tue, 04 Feb 2003 17:00:01 -0600
Directed to the Apple framework crew, is there a reason that some of the
controls, like NSTableView and NSBrowser, do not have an inactive or
disabled state? Even the NSBox lacks the ability to disable its contents.
This is odd considering that every control that I've used (I'm sure there is
at least one exception to this) in the HIToolbox under Carbon have inactive
and disabled states, and even use the embedding hierarchy to deactivate and
disable their children automatically.
These controls can be used in situations where user interaction needs to be
blocked, but the display of information is either still needed or is
unimportant. It would be simplest to use setEnabled: and turn them off, but
so far I've have had to hack around the deficiency by doing things like
change the selection, trap user selections and manipulate cells on
NSTableViews. For NSBoxes, I have to walk the hierarchy of children,
disabling them if possible. And I'm currently trying to figure out a method
for NSBrowsers.
Have I simply missed a more fundamental approach in Cocoa, or should this be
added to the bug list for future enhancements?
Brock Brandenberg
----- industrial design @ www.bergdesign.com ------
_______________________________________________
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.