dlls/ole32: Silence a FIXME

[Nikolay Sivov]

On 25.05.2015 12:44, Hugh McMaster wrote:
> On Mon, 25 May 2015 10:21:53 +0200, Stefan Dösinger wrote:
>> Am 2015-05-25 um 07:56 schrieb Hugh McMaster:
>>> This fixme appears on wine init either before console output or
>>> after it. The fixme text is interrupting the output for Wine's
>>> CLI-based programs, making the output difficult to read.
>> WINEDEBUG=-all is the best way to deal with disturbing debug output.
>> Or if you want other fixmes WINEDEBUG=-ole helps for this specific one.
>
> Thanks for the tip.
>
>> Though in many other places trying to QI an unknown interface is a
>> WARN, not a FIXME. Which interface(s) are the application(s) / other
>> libs trying to QI?
>
> The fixme appears every time wine launches an app, so WARN wouldn't help with this issue, although it may be more in keeping with the rest of the codebase.
>
> Searching on iid {00000019-0000-0000-c000-000000000046} brings up an MSDN page an OLE interop, the IExternalConnection Interface.
>   		 	   		
>

It probably comes from explorer, we should silence it there.