Stub DDE interface for Progman.exe
robertshearman at gmail.com
Fri Feb 6 04:41:13 CST 2009
2009/2/5 Jeremiah Flerchinger <jeremiah.flerchinger at gmail.com>:
> On Thu, 2009-02-05 at 18:12 +0000, Rob Shearman wrote:
>> 2009/2/3 Dmitry Timoshkov <dmitry at codeweavers.com>:
>> > "Jeremiah Flerchinger" <jeremiah.flerchinger at gmail.com> wrote:
>> >> Stubs basic DDE interface of Progman.exe. Similar to Progman stub in
>> >> shell32.dll. Both will need to be extended and a 3rd progman interface
>> >> will need to be added in user32.
>> > Progman DDE interface should be implemented by shell32.dll, nowhere else.
>> And it already is: ShellDDEInit.
>> All it needs is some always running process to call it. It looks like
>> explorer would be a good choice.
> Is explorer always running in Wine? I know "wine explorer" does not run
> ShellDDEInit when it starts. I thought most people were against
> additional processes, but I want to see the Progman DDE interface
> working for the different ways of calling it.
Try running a simple winelib app with WINEDEBUG=+process set and see
> ShellDDEInit didn't exist before Win 2000 and was in Shdocw.dll and not
> shell32.dll. Do we want to call ShellDDEInit in shell32 when Wine starts
> (and ends) then?
I'm not sure if there is a desire to allow native shell32 to be used
in Wine. However, if there is it would be simple to use GetProcAddress
with appropriate checks on the shell32 module that has been loaded.
> It is supposed to be called only by the process that is
> acting as the shell when it registers itself as a DDE host for the
> shell. I don't think anything else would ever call it then.
I can't work out what you mean by this. Perhaps you can rephrase it or
describe in more detail what you mean.
More information about the wine-devel