(03-29-2018, 04:14 AM)davenovo Wrote: The other feature I am looking for is how to make the modal dialog blocking. For example, in a VCL application I can write

result:=InputQuery(a,b,c)

or better yet I can have my own form with an .Execute method, and the Execute method calls showModal and does not return until the modalResult is set.

and the code wont continue until the user presses ok or cancel on dialog.

The examples I have seen launch the modal dialog in some button click, but then continues processing in the OnClose of the modal window. However, it is annoying to have to code that way, i.e. have to continue processing in another method from the one that generated the dialog.

Is there a way to mimic the standard modal dialog approach of the VCL with intraweb? Especially when I have custom search dialogs etc where I want to do something like

if SeachParamsForm.Execute then
begin
 // get the search criteria from the form
 //execute the search
end

(03-22-2018, 06:37 AM)DanBarclay Wrote:

(03-20-2018, 04:30 AM)davenovo Wrote: Hi Daniel,

To each their own I suppose. If you want to keep 7 dialogs worth of controls on a single form and it works for you, that is awesome. Now, for those that want to keep a single dialogs worth of controls on a single form, and just open that form modally instead of just calling .Show, I am wondering if there is a way to do that.

I do it the way you are talking about and it works fine.  I create my dialogs separately, then load them onto the form during the OnCreate.  I don't do it just to avoid having to deal with a busy design time form (though that is helpful), I do it so that I can use "common dialogs" (of my own requirements) on multiple forms easily.

I create my dialog "content" as frames.  As usual, fill the frame with a region then put your stuff on the region.  During form OnCreate I call a procedure that creates the frame (from the frame design time class) on the form, sets Parent to the form, Visible to false, and the frames' region visible to false.  Then you can use the regions in dialogs.  Don't forget to set RenderInvisibleControls to True on the dialogs.

It has been a while since I did all that, but I'll try to respond if you run into problems with it.  It should work without too much difficulty.

Dan

(05-31-2019, 03:20 AM)DanBarclay Wrote: Depending on the one you want to show, assign the region for that dialog to the TIWModalWindow.ContentElement instance on your form.  You can make/change that assignment during execution.

Note that the RenderInvisibleControls must be set prior to creating the form itself, not when you try to show the dialog if you are async.

Sorry for the short answers.  I don't have any simple code to post, and I'm reworking my machine right now anyway.  SSD's are wonderful.


 

Code:

    with IWModalWindow1 do
       begin
        Reset;
        Buttons.CommaText := '&Ok,&Cancel';
        Title := 'Filter';
        if FiltroStuff then 
          begin
            ContentElement :=FFrameFiltro.IWFrameRegion;
            OnAsyncClick := FrameFiltroDoOnAsyncClick;
          end
         else
          begin
            ContentElement :=SomeOtherDialog.IWFrameRegion;
            OnAsyncClick := SomeOtherDialogClick;
           end;
        Show;
       end;

Dan