With macOS 26 (not sure about other versions), the wxFontPicker is not picking up ANY of the other attributes other than base font name and size. Bold, Italic, Underline, etc... are not coming through.
Expect that the font that is picked is actually returned and is queryable with the properties the user selected.
This is easy to reproduce in the "widgets" sample. Open the widgets same, select the FontPicker, set the font to something like "Arial Bold 24" and all that is returned is just "Arial 24".
NOTE: a possible separate bug: in the font picker that pops up, if you click on the button to enable the Typographical panel, the widgets app completely crashes.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
This looks bad, I'll try to have a look but, thanks for reporting.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Sorry, I forgot that I still can't really debug this because I still haven't updated to macOS 26.
@csomor Might I ask for your help again here?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@vadz I'll look at it
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@dkulp Thanks for your report!
Just to make sure we are talking about the same thing:
the log information currently does not log the numeric weight at al, nor the style, so it should be logged, with something like
wxLogMessage("The font changed to '%s' with size %d, style %s, weight %d !",
event.GetFont().GetFaceName(), event.GetFont().GetPointSize(),
event.GetFont().GetStyle() == wxFONTSTYLE_NORMAL ? "regular" : "italic",
event.GetFont().GetNumericWeight());
Now on Tahoe the selection of the variant always jumps back to Standard, I'll try to find out what events we must support here... I do not get a crash with the typography panel, but as we try to get a modal behavior this does not fit in right now.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Using your log message, I'm ALWAYS getting style regular and weight 400 no matter if I select italic or bold or not.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Using your log message, I'm ALWAYS getting style regular and weight 400 no matter if I select italic or bold or not.
Yes, I know, under Tahoe the selection always jumps back, it is not persistent, eg, select the bold variant, change the font size, the variant jumps back to standard, I assume it is now depending on some external "state" which we must provide, that gets changed and queried ...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
the panelConvertFont method of the Font Panel does not convert the font correctly, missing weight and style on many fonts, this also happens when I directly log the NSFont
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
I didn't find any mention of problems with panelConvertFont but no current usages either, so I'll guess I'll remove that line and store a reference to the current font in the delegate which gets notified of every change, and that one is still accurate even unter Tahoe.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@dkulp could you please re-test ? Thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Definitely works much better. Interesting note: italics wasn't working for me, but that turns out that xLights has never supported italics fonts. No one has ever reported it. :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()