🚀 go-pugleaf

    Hello Dan,

    I believe this can be accomplished via the registry.
    I'm not certain but I believe that the actions involved
    in this context are the same as those that occur when
    you do the same thing in windows explorer. I think that
    you can trap this action and process the actions you describe...

    HTH?

    Bruce Larrabee

>    I believe this can be accomplished via the registry.

Any idea where I can find a reference or an example for this?

I dread attempting to rewrite the functionality provided by TOpenDialog 
or TSaveDialog; I would think creating a descendant class from one of 
those would be easy, and then adding a TButton to popup a keyboard, or 
capturing the double-click message wouldn't be that hard; but I'm not 
having too much luck.

Is what I am trying to do possible?

"Dan Mayo" <do_not_spam_dmayo2@netzero.com> wrote in message
news:45cca151$1@newsgroups.borland.com...

> I would think creating a descendant class from one of those
> would be easy, and then adding a TButton to popup a keyboard

Yes, that is doable.  In the OnShow event, you have access to the HWND
of the dialog.  You can use the Win32 API to add/modify anything in
that HWND as desired.  You can even create VCL controls.  Simply set
their ParentWindow property to the HWND of the dialog.

> or capturing the double-click message

Again, using the OnShow event, you can use Get/SetWindowLong() to
subclass the HWND of the edit box so that you can intercept the
WM_LBUTTONDBLCLK message directly.


Gambit

Dan Mayo wrote:
>>    I believe this can be accomplished via the registry.
> 
> Any idea where I can find a reference or an example for this?
> 
> I dread attempting to rewrite the functionality provided by TOpenDialog 
> or TSaveDialog; I would think creating a descendant class from one of 
> those would be easy, and then adding a TButton to popup a keyboard, or 
> capturing the double-click message wouldn't be that hard; but I'm not 
> having too much luck.
> 
> Is what I am trying to do possible?


Reading the Help file, it looks like I can get the Handle for the 
TOpenDialog in the OnShow event.  I was thinking that if I had the 
handle, then I could create a button and add a button to that dialog, 
such as the following:

//OnShow()....
    Button->Top = 0;
    Button->Height = 10;
    Button->Left = 0;
    Button->Width = 10;
    Button->Caption = "HELLO";
    Button->Parent = NULL;

/* <- This places it on the main form, but obviously is inaccessible as 
the dialog is modal during execute()*/
    //Button->Parent = Application->MainForm;


    Button->ParentWindow = this->Handle; //I figure this would do it, 
but it doesn't
    Button->Visible = true;
    Button->BringToFront();


Any ideas?  Or am I barking up the wrong tree again?

Why doesn't the below code show the EditBox in the SaveDialog on the 
OnShowEvent?

    Edit1->Parent = NULL;
    Edit1->ParentWindow = NULL;
    Edit1->ParentWindow = OpenDialog1->Handle;
    Edit1->Top = 0;
    Edit1->Height = 1000;
    Edit1->Left = 0;
    Edit1->Width = 1000;
    Edit1->Text = "HELLO";

    Edit1->Visible = true;
    Edit1->BringToFront();
    Edit1->Refresh();
    Edit1->Repaint();


If I have Edit1 on the main form, Button1 calls the 
SaveDialog->Execute(), when Button1 is clicked, the above code runs (as 
I can see from both breakpoint watching and noticing Edit1 disappear 
from the mainform), but the Edit1 Box is no where to be seen on the 
SaveDialog box.

What is wrong?

Nevermind, I have to use the GetWindowLong...
that works.  Thanks!

"Dan Mayo" <do_not_spam_dmayo2@netzero.com> wrote in message
news:45ccc478$1@newsgroups.borland.com...

> Reading the Help file, it looks like I can get the Handle for the
> TOpenDialog in the OnShow event.

You can.  What the help does not tell you, however, is that you need
to use the Win32 API GetParent() function to get the *corrent* HWND to
use from the dialog's Handle property.

> I was thinking that if I had the handle, then I could create a
button
> and add a button to that dialog

You can.

>     Button->ParentWindow = this->Handle; //I figure this would do
it,
> but it doesn't

That is the wrong Handle to use.  The event handler is a member of
your TForm class, so the 'this' pointer will point to the instance of
your TForm.  Thus, you are using the TForm's HWND as the parent window
instead of the dialog's HWND.  You need to use this instead:

    Button->ParentWindow = ::GetParent(SaveDialog1->Handle);


Gambit

"Dan Mayo" <do_not_spam_dmayo2@netzero.com> wrote in message
news:45cce52f@newsgroups.borland.com...

> Why doesn't the below code show the EditBox in the SaveDialog
> on the OnShowEvent?

Because you are still using the wrong HWND as the ParentWindow.  See
my other reply.


Gambit

Ok, button is added, the onclick event is assigned to the button; but 
the onclick event never is fired when the button is clicked?  Why not?

What is the best way to modify the file name editbox when the 
TOpenDialog is already visible?

"Dan Mayo" <do_not_spam_dmayo2@netzero.com> wrote in message
news:45cfa974$1@newsgroups.borland.com...

> Ok, button is added, the onclick event is assigned to the button;
but
> the onclick event never is fired when the button is clicked?  Why
not?

Because the dialog window is not a VCL window.  It is not designed to
forward the messages that are needed for triggering the button's event
handlers.  You will have to use Get/SetWindowLong() to subclass the
dialog's window in order to handle the WM_COMMAND/BN_CLICKED
notification directly.  Otherwise, put the TButton onto a TPanel or
other container, and then put that onto the dialog window.

> What is the best way to modify the file name editbox when the
> TOpenDialog is already visible?

You already know how to obtain the HWND of the dialog window.  Once
you have that, you can do whatever you want with it and its child
windows.  All you need is their HWNDs as well, which you can get using
FindWindow/Ex() or GetDlgItem().


Gambit

Thank you; I got it completely working now.  It took me a while to find 
the right ID for the edit box since I was trying to browse 
documentation/web to find the appropriate constant; what is the best 
way?  I basically ended up making a loop to get window text from 
incrementing IDs, and then displayed the ID and the text, if found; from 
that I could correlate the ID to the editbox.

"Dan Mayo" <do_not_spam_dmayo2@netzero.com> wrote in message
news:45d08da4$1@newsgroups.borland.com...

> It took me a while to find the right ID for the edit box since I
> was trying to browse documentation/web to find the appropriate
> constant; what is the best way?

Use Microsoft's Spy++ or Borland's WinSight utilities.


Gambit