🚀 go-pugleaf

"Tom" <tom@net.com> wrote in message
news:43b26430$1@newsgroups.borland.com...

> Because I have the same options but I also have a TimeEdit
> so any of this options can be executed at desired time

What do you mean exactly?  Are you providing a timeout value, ie "Execute
such-and-such option in NN seconds"?  Or are you implementing an absolute
timer value, ie "Execute such-and-such option at NN:NN:NN AP on NN/NN/NNNN"?
If the former, then I can understand wanting to replace/augment the dialog.
But if the latter, then why not provide that type of configuration inside
your own application completely separately from the OS's dialog?  Again, I
ask, what EXACTLY are you trying to accomplish?

> and that's why I wanted to replace the standard dialog with
> my application, I thought it would be nice to call my application
> via Start->Turn Off Computer.

Rather than replace the existing dialog altogether, you can try keeping the
existing dialog and just alter it directly as needed.  Write a DLL that
calls the SetWindowsHookEx() function to install a WH_CBT hook into the OS.
When the DLL receives a HCBT_ACTIVATE notification, you can check if the
specified HWND is the dialog or not, and if so then alter it any way you
wish, such as by adding additional controls to it.  You can also use a
WH_CALLWNDPROC and/or WH_CALLWNDPROCRET hook to respond to messages that are
issued for your extra controls.


Gambit