Re: Borderless NSColorWell: bug or feature?
Re: Borderless NSColorWell: bug or feature?
- Subject: Re: Borderless NSColorWell: bug or feature?
- From: Andy Lee <email@hidden>
- Date: Sun, 28 Dec 2008 02:11:14 -0500
On Dec 28, 2008, at 1:37 AM, WT wrote:
Nothing to click? What about the area inside the border, the part
that shows the color the control is set to? Incidentally, I just
tried clicking on the very center of a bordered color well and it
did show the color panel, so it's not true that you have to click on
the border to have the panel show up.
You're right, I should have checked that. I agree it's unclear
whether the borderless behavior is intentional. I think it should be
either a documentation request or an NSColorWell bug.
Besides, the border is rather small and it wouldn't make much sense
to require such precise clicking when there's generally a much
bigger area the user can click on to get the desired effect.
I actually think the border is rather large -- certainly as easy to
click as a split view's divider, although a split view gives you
visual feedback when the mouse is over the divider to make it easier.
The fact that a color well gives no such feedback should have been a
clue that the border isn't a special area.
For some reason I had thought the internal part was only for dragging
color swatches. In all these years I never noticed that it brings up
the color panel if you click it.
--Andy
Wagner
On Dec 28, 2008, at 7:27 AM, Andy Lee wrote:
The border is the part you click to bring up the color panel. If
you take away the border, there's nothing to click.
--Andy
On Dec 28, 2008, at 1:10 AM, WT wrote:
Hello,
I just found by experimenting with NSColorWell objects that merely
setting them borderless in IB disables their ability to show the
color selection panel. Looking at the NSColorWell class reference
document, the "Choosing Colors With Color Wells and Color Panels"
document, and the "Human Interface Design" document, I could not
find any mention of that fact.
Why should a control's border affect the control's ability to
perform its function? Is that supposed to be a feature, or is it a
bug?
Wagner
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden