🚀 go-pugleaf

"Mike Collins" <mikec@kr8.co.uk> wrote in message
news:4019701c@newsgroups.borland.com...

> 1) At design-time run a program like ExeScope or ResHacker
> to examine the DLL's resource section in order to look at the
> resource script for the dialog box get the ID's of the controls
> that I need to access.

You could also use WinSight or Spy++ at runtime for that.

> 2) At run-time call FindWindow() to get a Handle to the dialog.

That will only work if the Caption of the dialog does not change at runtime.

> 2) Since I have a handle to the dialog and the ID of the control I
> should be able to use SendDlgItemMessage() to 'issue' command
> to the various controls?

Yes.

> If it is as I think, any pointers on which messages to send to
> enable / disable buttons, set text in buttons and edit box's,
> based on the fact that it's all been written in VC++.

The fact that it is written in VC++ is irrelevant.  Controls in dialogs are
normal controls like any other, they are still created using
CreateWindow/Ex().  The Win32 API documentation has tons of sections
regarding messages for normal buttons, edits, etc.

> Finally, is there anyway to 're-direct' what happens when a
> certain control is accessed i.e. I want to re-direct one of the
> buttons on this dialog so when the user clicks on it, my own
> code is executed instead of the DLL's code.

You need to subclass the dialog's window procedure, or alternatively use
amessage hook via SetWindowsHookEx().


Gambit