Page 2 of 2
Re: Bug with fonts for StringGadgets?
Posted: Tue Dec 11, 2018 12:06 pm
by Dude
Fred wrote:I don't think it's a PB issue
ccode wrote:I also do not see it as a bug
Can I convince you both with this example?
Code: Select all
OpenWindow(0,200,200,320,120,"Exact same font, different gadgets",#PB_Window_SystemMenu)
f=LoadFont(1,"@DFPOP1-W12",13,#PB_Font_Underline)
StringGadget(1,10,10,300,40,"Underlined StringGadget")
SetGadgetFont(1,f)
EditorGadget(2,10,60,300,40)
SetGadgetText(2,"Underlined EditorGadget")
SetGadgetFont(2,f)
Repeat : Until WaitWindowEvent()=#PB_Event_CloseWindow
Re: Bug with fonts for StringGadgets?
Posted: Tue Dec 11, 2018 12:54 pm
by RASHAD
Hi Dude
It can be when Windows can not find the mentioned font and sub. it with another font
Try any known font like Tahoma or Arial and see the result
Re: Bug with fonts for StringGadgets?
Posted: Tue Dec 11, 2018 12:59 pm
by Dude
But Windows obviously did find the font because it's shown correctly in the EditorGadget. Just not shown correctly in the StringGadget. And as mentioned in my first post, the underline font works in other apps, such as Paint Shop Pro. Just not in PureBasic's StringGadget. It can't get any more obvious than that.
Other fonts work fine. The problem is, my app has a font preview feature, and if customers are previewing with underline, and no underline appears, then I'm going to start getting support emails saying my app is buggy.
Re: Bug with fonts for StringGadgets?
Posted: Tue Dec 11, 2018 1:05 pm
by RASHAD
To be sure Run font from control panel and search for yours before you judge the effect (Search also if that font has underline too)
And do not depend on instantaneous install(check if the font file in the fonts folder)
Then if it still there we can give it more investigation
And do not get sad
Re: Bug with fonts for StringGadgets?
Posted: Tue Dec 11, 2018 2:26 pm
by Fred
Could you try with an EDIT control with API and see what happen ?
Re: Bug with fonts for StringGadgets?
Posted: Tue Dec 11, 2018 4:17 pm
by skywalk
No problem with PB v57b4 on Windows 10 Pro.
No api required.