Hi Detlef.

--- In [email protected], "dleidinger" <[EMAIL PROTECTED]> wrote:
> If it's not to hard and to difficult to explain, it would be very 
> kind, if you could answer those questions.

Sure.

> You proposed the following popwerpro-command (it's a chainend 
> command, isn't it?):
> win.handle("filedialog","FolderView").parent.sendMessage
(0x111,28716,0)
> In other words:
> win.sendmessage(win.parent(win.handle
("filedialog","FolderView")),0x111,28716,0))
> correct ?

Yes. I'd prefer it chained, though.

> My questions:
> - Where do you know the win.handle-parameters from ?

This is something special about Explorer-windows. In Girder you see 
that the command has to be sent to the child window of 
class "SHELLDLL_DefView". (The great thing about Girder is that you 
can actually try out the commands, which helps a lot in finding the 
right message.) Now, "SHELLDLL_DefView" cannot be seen directly by 
PowerPro win-commands for some reason. But the window of the 
class "SysListView32" can be seen. It's name is "FolderView" and it's 
a child of the SHELLDLL_DefView-window (you can see this in some 
windows examination tools, e.g. WinExplorer from NirSoft). 
So the command above is really just a workaround to get to the handle 
of the SHELLDLL_DefView-window (needed for the message) without using 
the dll-plugin. 
Normally I'd use "FindWindowEx" fron the Win-API for this. I posted 
this before:
http://tech.groups.yahoo.com/group/power-pro/message/31812

> - What is "0x111" ?

In the column "Type" of the capture-window you see "Command", which 
means that this message is of the type WM_COMMAND. WM_COMMAND is 
defined in a windows header-file as a constant. It's actually a 
number: 0x111 (or 273, if you prefer). You need this as the first 
argument for sendMessage.

Mockey


Reply via email to