Issue-#108 BlackBox Start up warnings

[DGDanforth]

New version:
http://blackboxframework.org/unstable/i ... a1.476.zip

Ivan's version works as luowy has specified.

-Doug

[DGDanforth]

For the record my version of comctl32.dll is 5.82.2900.6028

[Ivan Denisov]

Does this issue ready for voting?

[DGDanforth]

If you have Dependency Walker on your machine you can examine comctl32.dll and see it references a large number of other dlls such as
user32 and kernel32, ...

-Doug

[DGDanforth]

Does this issue ready for voting?

I(like Josef) want to know why explicit loading of comctl32.dll is necessary for XP but not for other versions of Windows.
-Doug

[DGDanforth]

Ah, this may be it.
Enabling Visual Styles
https://msdn.microsoft.com/en-us/librar ... 85%29.aspx

[Josef Templ]

Does this issue ready for voting?

No, it is obviously not ready.

[Josef Templ]

For the record my version of comctl32.dll is 5.82.2900.6028

I checked my versions with Dependency Walker.

Actually, I have two versions of COMCTL32.DLL on my XP.
One is 5.82 in Windows/System32 (size=617.472)
and one is 6.0.2600.6028 in Windows/winsxs/... (size=1.054.208).

The 5.82 version is used for ObxTest without the manifest,
the 6.0 version is used with the manifest, exactly as luowy has pointed out before.
The 6.0 version must have been installed via some service pack. That's why it is in winsxs.

For me there are still open questions:

1. what is WinApi.GetLastError() after a failed call of MessageBoxW?
This is the standard way to debug a function call that does not work.

2. is loading of comctl32.dll really required or is it accidentally producing a side effect
that causes the test to work, e.g. a time delay. As far as I see comctl32 is not used for MessageBoxW,
so it is really surprising to see this dependency in the bug fix.
Maybe GetLastError gives us an answer to this question.

- Josef

[DGDanforth]

Wow, I actually have 9 versions under WinSxS.
The most recent seems to be
Version 6.0.2900.6028
size (1,054,208 bytes)
modified Monday, August 23, 2010, 9:12:02 AM

[DGDanforth]

1. what is WinApi.GetLastError() after a failed call of MessageBoxW?
This is the standard way to debug a function call that does not work.

I gave a stab at finding out but how does one tell the user what the message text is?
I have coded how to get that text but since Kernel does not import Dialog or StdLog
I don't know how to report it.

Also, when I put a HALT into the code after that call (I believe) what happens is a just in time debugger error message
rather than a trap handler.

-Doug