FROM : Sean McBride
DATE : Tue Mar 04 00:19:53 2008
On 3/3/08 2:56 PM, Nick Zitzmann said:
>I checked the archives and didn't see anything. How do I set the image
>to display in a pull-down NSPopUpButton using Interface Builder 3.0?
>No matter what I type in the image field, the field is always cleared
>out, and no image is displayed.
I filed this bug in July <radr://5357188> and was told:
"As for the issue with the pop-up button, you are running into a
mismatch between the AppKit API for controls. NSButton does provide a
setImage: API, but if you inspect the API for NSPopUpButton you'll find
the following description:
- (void)setImage:(NSImage *)anImage
This method has no effect.
NSPopUpButton does not respond to this API at all. Our inspectors
expose the API by concrete class, which is why the field to set the
image is listed on NSButton's inspector slice. We do not attempt to
disable controls in inspector slices based on what the subclasses
respond to - we have no means to validate that or support it long term.
As a result, this is a duplicate of the bug we have to track this
difference, Bug ID# 5024840."
--
____________________________________________________________
Sean McBride, B. Eng <email_removed>
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
DATE : Tue Mar 04 00:19:53 2008
On 3/3/08 2:56 PM, Nick Zitzmann said:
>I checked the archives and didn't see anything. How do I set the image
>to display in a pull-down NSPopUpButton using Interface Builder 3.0?
>No matter what I type in the image field, the field is always cleared
>out, and no image is displayed.
I filed this bug in July <radr://5357188> and was told:
"As for the issue with the pop-up button, you are running into a
mismatch between the AppKit API for controls. NSButton does provide a
setImage: API, but if you inspect the API for NSPopUpButton you'll find
the following description:
- (void)setImage:(NSImage *)anImage
This method has no effect.
NSPopUpButton does not respond to this API at all. Our inspectors
expose the API by concrete class, which is why the field to set the
image is listed on NSButton's inspector slice. We do not attempt to
disable controls in inspector slices based on what the subclasses
respond to - we have no means to validate that or support it long term.
As a result, this is a duplicate of the bug we have to track this
difference, Bug ID# 5024840."
--
____________________________________________________________
Sean McBride, B. Eng <email_removed>
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
| Related mails | Author | Date |
|---|---|---|
| Nick Zitzmann | Mar 3, 22:56 | |
| Jens Alfke | Mar 3, 23:21 | |
| Nick Zitzmann | Mar 3, 23:32 | |
| Ken Ferry | Mar 3, 23:57 | |
| Nick Zitzmann | Mar 3, 23:59 | |
| Sean McBride | Mar 4, 00:19 | |
| Steven Degutis | Mar 4, 03:01 |






Cocoa mail archive

