NSPopUpButton with InlineButton style logs "Unknown bezel style 15 and/or control size 1"

867 views Asked by At

I have an NSPopUpButton with Inline Button style. When mouse enters, exits or mouse down or mouse up, it logs "Unknown bezel style 15 and/or control size 1"

15 is the NSInlineButtonStyle from NSButtonCell.h

typedef NS_ENUM(NSUInteger, NSBezelStyle) {
    NSRoundedBezelStyle          = 1,
    NSRegularSquareBezelStyle    = 2,
    NSThickSquareBezelStyle      = 3,
    NSThickerSquareBezelStyle    = 4,
    NSDisclosureBezelStyle       = 5,
    NSShadowlessSquareBezelStyle = 6,
    NSCircularBezelStyle         = 7,
    NSTexturedSquareBezelStyle   = 8,
    NSHelpButtonBezelStyle       = 9,
    NSSmallSquareBezelStyle       = 10,
    NSTexturedRoundedBezelStyle   = 11,
    NSRoundRectBezelStyle         = 12,
    NSRecessedBezelStyle          = 13,
    NSRoundedDisclosureBezelStyle = 14,
    // The inline bezel style contains a solid round-rect border background. It can be used to create an "unread" indicator in an outline view, or another inline button in a tableview, such as a stop progress button in a download panel. Use text for an unread indicator, and a template image for other buttons.
    NSInlineBezelStyle NS_ENUM_AVAILABLE_MAC(10_7) = 15,

    NSSmallIconButtonBezelStyle NS_ENUM_DEPRECATED_MAC(10_0, 10_0) = 2 // This bezel style is obsolete and should not be used.
};

Oddly, everything compiles fine, and I set the style in Interface Builder. Everything also works fine except for this console spew.

I was unable to find anything in the docs or the headers for NSButton, NSPopUpButton, NSButtonCell, NSPopUpButtonCell, NSMenuItemCell that warn or prohibit this style. And the size is set by constraints with no auto layout issues logged.

The spew to the console does not contain any indicator of where this message comes from. I can only tell by observed behavior.

Unknown bezel style 15 and/or control size 1

Is there a way to silence this?

1

There are 1 answers

4
uchuugaka On BEST ANSWER

Currently it seems to be a bug.