Passing AI4Win test for win32 list controls in report mode with only partially visible columns

[skuskusku]

How can I pass an AI4Win test for a list control in report mode with partially visible columns

My application uses a win32 list control from comctl32 in report mode as a child of a dialog window. It has 10 columns. By default, it happens to come up with 4 columns fully visible and from the fifth column, only a few pixels are shown for each list items fifth subitem. Now for every list control item, an AI4Win test complains about the subitems in the fifth column (which is only partially, i.e. only a few pixels, visible).

The error text goes like this: "The BoundingRectangle property must represent an area of at least 25 pixels."

The suggested fix is this: "Modify the BoundingRectangle property so that its width and height define an area of at least 25 pixels."

However, this dialog passes the AI4Win test, if I scroll the list control horizontally just a bit, or if I maximize the dialog whereby the list control is enlarged as well so all list control content is fully visible. I am a bit surprised that passing or failing a test with AI4Win depends on the scroll position of the list control. This is also not something I am having under control because we are persisting column widths and dialog sizes to the registry to show the dialog and its list control with the exact same column widths and size that it had the last time it was shown.

What can I do to pass the AI4Win test with this list control? Is there anything I can/should do?

Any help appreciated,

--
Stefan

[skuskusku]

I would like to add one thing: I can reliably only reproduce this if I set the scaling in display settings to 100%. I never managed to reproduce this for all visible list control items with any value higher than 100%. If I set display scaling to 125% I can only reproduce this error for the rightmost partially visible element of the last row, if this row is visible for only a few pixels in height. In that case the red rectangle in AI4Win that shows the erroneous element in the screenshot is only a very tiny one in the lower right corner.