dsa-t

> this looks worse than the current appearance under MSW You're right. wxBORDER_THEME (wxBORDER_DOUBLE) seems too thick on wxQt.

It calls `wxSystemSettingsNative::GetMetric(wxSYS_EDGE_Y)` -> 2 `wxSystemSettingsNative::GetMetric(wxSYS_BORDER_Y)` -> 2 So the size increases by (2+2)*2 = 8.

Now, trying to implement `wxBORDER_THEME` in wxQt, in `wxSearchCtrl::Create` I'm calling: ```cpp #include ... m_qtWindow->setStyleSheet("border: 1px solid blue; background: cyan"); ``` But it only changes the editable field:  Not...

Here's how it looks now on wxQt:  The total height matches normal textfield/combobox/button sizes.

At 200 dpi, borders and check/radiobuttons do not become bigger on wxQt with default style or other system apps. But they are scaled in Qt5 example. gtk2 (default) style: ...

The scaling on gtk2 can be enabled by setting env var `QT_AUTO_SCREEN_SCALE_FACTOR=1`   x2 scaling starts at 144 dpi

> whether creating a 100x100 window at 200% scaling creates a window 100 or 200 physical pixels wide/high? That gives 200 physical pixels when `QT_AUTO_SCREEN_SCALE_FACTOR=1`, otherwise 100, it looks like....

I haven't checked how it renders on Windows.

Looks fine on MSW: 

> Why is this necessary? To be inline with other Graphics APIs which limit the radius internally.