http://bugs.winehq.org/show_bug.cgi?id=27985
--- Comment #5 from Nikolay Sivov bunglehead@gmail.com 2011-10-25 13:32:49 CDT --- (In reply to comment #4)
Well the idea of the test is to show that having a column with the same size as the listview should not result in a visible scrollbar. I used the test bot to validate that windows does indeed behave that way.
I tested with ControlSpy just now and one-column list with no vertical scrollbar still gets a horizontal one if I set column width to whole control width. So some padding/nonclient size matters and gives scrollbar on native too, it's hard to tell what's going on with it.
I am not sure what you are asking about with "Does is use LVS_NOSCROLL", but as the test shows that windows doesn't show a scrollbar in that particular case even without any LVS_NOSCROLL flags.
If it uses LVS_NOSCROLL it probably disables scrollbar that's what I mean.
I think too that the width calculation is wrong, but I kept the test that way since I am unsure of how to get the calculated width. It's propably totally easy but I don't know how to do it and would have to dig trough MSDN documentation.
You mean width calculation is wrong in described case or in general?
So should I try to find out how to get the calculated width or do you want to write a proper test and patch?
Width calculation depends on text width, so tests will not be very reliable. What we need is a short enough log (+listview) that shows how control is created, column added etc.
I can't get trial version of this application I guess?