Incompatibility with Actual Window Manager, problem with foo_ui_std Options

[Alex Belyakov]

Hi there,

I'm a developer in Actual Tools. Recently, one of our users reported a strange incompatibility with our Actual Window Manager and foobar2000. It seemed that foobar's main window removed a window subclass, which our hooking library set to provide additional functions.

I've made a small research in fb2k's internals, and it seems that one of functions in foo_ui_std.dll checks GWL_WNDPROC in the main window, and resets it to a default value whenever it changes. In foobar2000 version 0.9.6.9, the function address in foo_ui_std.dll is 1009b570. The corresponding C-like code would be as follows:

CODE

if (m_Wnd && m_WndProcStub && (GetWindowLong(m_Wnd, GWL_WNDPROC) != m_WndProcStub)) {
SetWindowLong(m_Wnd, GWL_WNDPROC, m_WndProcStub);
}
return 1;

If I NOP calling SetWindowLong out of the code, our subclass is not removed from the main window, and all the fb2k's features seem to work fine.
Could you please consider removing or redesigning this part of your UI library, to make those who use both foobar2000 and our products happy?

Thank you in advance for considering this.
I can provide any additional technical info, if you need it.

This post has been edited by Alex Belyakov: Nov 19 2009, 06:16