```window.option_add("*font", ...)``` doesn't effect some buttons about sun-valley-ttk-theme

[rdbende]

Do you mean the buttons in the red circle? ? It maybe because Windows10 doesn't have a correct Segoe UI font...

So they look like that even without your .option_add() call?

[rdbende]

The font of those buttons is definitely weird, but it's not the default, so something is working.

[littlewhitecloud]

The font of those buttons is definitely weird, but it's not the default, so something is working.

Do you mean the buttons in the red circle? ? It maybe because Windows10 doesn't have a correct Segoe UI font...

[littlewhitecloud]

Yes, I think.

[littlewhitecloud]

It seems that the ttk.Button widget doean't follow the window.option_add("*font", ...)

[rdbende]

That's quite unlikely, because it does for me.
However, why don't you use a ttk.Style for configuring the font of the button? Is it not working either?

[littlewhitecloud]

Yes.

[rdbende]

Can you show a screenshot with this line commented out, and another one with the font set to something other than Cascadia Mono?

[littlewhitecloud]

[rdbende]

Wait, comparing these last two screenshots to the first one, it appears, that your font actually gets applied to those buttons, even though it looks a bit bad.

[littlewhitecloud]

LOL, it is still the default font.

[littlewhitecloud]

[littlewhitecloud]

Seems that button doesn't follow the settings

[littlewhitecloud]

forget to say that I am using sv_ttk 2.0 and after I upgrading to 2.5.3, It looks more bad

[littlewhitecloud]

It seems that sv_ttk 2.0 still can show Seoge UI font correctly on Windows 10......

[rdbende]

after upgrading to 2.5.3, it looks worse

In what aspect?

Seems that button doesn't follow the settings

What settings? You just proved, that adding

config.option_add("*font", ("Cascadia Mono", 9))

actually changes the font:

With default font

with your Cascadia Mono font:

[rdbende]

It seems that sv_ttk 2.0 still can show Seoge UI font correctly on Windows 10......

I can't understand why the same font is called differently on Windoze 10 and 11
Will fix that.

[littlewhitecloud]

after upgrading to 2.5.3, it looks worse

In what aspect?

Seems that button doesn't follow the settings

What settings? You just proved, that adding

config.option_add("*font", ("Cascadia Mono", 9))

actually changes the font:

With default font

with your Cascadia Mono font:

No, actually, it is still the consola font with the latest screenshot.

[littlewhitecloud]

Any font will fail to apply the button not only cascadia mono font