Re: [wsjt-devel] Button sizes not correct

[Laurie, V. <_vk...@vk...>]

On 01/09/2023 7:11 pm, Rick via wsjt-devel wrote:
>
> This effect is not present in Linux Mint. (1920x1080 screen, font Noto 
> Sans Bold Italic 12)
>
> However, looking at the code in the Qt development environment this 
> clipping effect can be seen. These buttons all have a minimum width of 
> 32 and the default font size is 12.  Otherwise the size policy for 
> these buttons is the same as for the Tx 1-6 buttons.
>
> With a button width of 32 the max font size for no clipping is 9. With 
> font size of 12 the minimum button width is ~48.
>
> You can change the font size in Settings | General | Font. Reducing it 
> will help, but it will affect the entire window and I suspect you may 
> have tried that already and found it unacceptable.
>
> It might also be worthwhile checking that the font you have selected 
> actually exists on your machine and is not being substituted, which 
> can cause weird effects.
>
> You could just run the app with a larger width. At some point the 
> buttons will expand.
>
> As a last resort, there is an easy code fix for this. Just go into the 
> mainWindow.ui and change houndButton | minimumSize | Width.  Setting 
> it to 0 (on all six buttons) allows the application to scale the 
> button width in accordance with the combined sizing policies. However 
> changing just the houndButton from 32 to 48 is sufficient and doesn't 
> introduce any other sizing effects. Recalculate the md5 checksum. 
> Recompile and voila.
>
> HTH
>
> Regards
>
> Rick (GM4JIB)
>

This incorrect button sizing is being applied to the mode selection 
buttonsonly, no other buttons.
Font type and size cannot be the cause. No other UI elements are affected.

Several previous tests have shown it is only occurring on high DPI 
monitors, 4K monitors in my case, running Win10 & Win11.

IMO, the code to calculate button size based on text font metrics is not 
correctly calculating the width for high dpi situations.

My C++ skills are 30 years out-of-date so  am unable to offer any advice 
as to the cause.

de Laurie VK3AMA