CommonControls (Replacement of the MS common controls)

[Krool]

The problems are not limited to the ScaleX/Y functions and the Screen.TwipsPerPixelsX/Y properties, the position and size of the controls that VB handles automatically are also affected.

I know. The size will be "corrected" already within UserControl_Resize. In a way that afterwards .ScaleWidth etc. will report correct.
That point with himetric conversion was only an additional issue.

[Eduardo-]

I know. The size will be "corrected" already within UserControl_Resize. In a way that afterwards .ScaleWidth etc. will report correct.
That point with himetric conversion was only an additional issue.

Yes, you can make the controls to work properly on non integer TwipsPerPixelsX/Y values and that's very nice, and for some projects it will be a solution, but in most cases VB still won't work properly, because it will position and size the forms wrongly, and if the program uses Screen.TwipsPerPixelsX/Y to position controls (or for other purposes) it will report a wrong value. Also ScaleX/Y of the forms will fail.

Unfortunately, we'll need a fix on VB itself to solve that.