Running crossbuilt tests for comctl32 showed some failures when version 6.0 used:
27 - imagelist 25 - rebar 130 - toolbar
(version 6.0 module used through external manifest xml in my test) Toolbar and rebar failures show different rectangle coordinates (all toolbar fails are about -2 shift of y coord).
I've some questions:
0) What way is better to implement this 6.0 module - using WinSxS creating another separate version 6 and act like Win, or extend existing module (with version checking probably see next question)? 1) the main is about imagelist: why are we relying here on internal storage format? Tests show that on 6.0 this format's changed.
If the reason is to get the same structure when writing to IStream (to be compatible with streams saved on native platform) here's another question => 2) Since wine module should be able to support "all" versions of native ones we need to run tests on both versions on Windows. Is there any way to do so easily maybe playing with activation contexts?
The reason why I'm interested in that is the implementation of interfaces IImageList (followed by IImageList2) and related calls
HIMAGELIST_QueryInterface from comctl32 (6.0) SHGetImageList from shell32
All this comes from http://bugs.winehq.org/show_bug.cgi?id=15885
Any thoughts are appreciated.
Nikolay