• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 378
  • Last Modified:

Bypassing FormShow(Sender: TObject) Event

Hi,

I check for a certain condition on application startup in the FormCreate procedure. If the condition is not met, I do not want the applkication to the show the form by running FormShow. What code can I use to show the form OR not show the form depending on the condition being true or false in FormCreate?

Regards

Pierre
0
barnarp
Asked:
barnarp
  • 3
  • 3
  • 2
  • +2
2 Solutions
 
LRHGuyCommented:
I think you have two different issues.

You can disable the call to the FormShow event by setting OnFormShow to nil:
  OnFormShow:=nil;

If you do that in FormCreate, then the FormShow event you've defined will not be called.

But, that does not stop the form from being shown. Depending on the type of form, and how it's being called, you might be able to set visible to false. Is this the main form?
0
 
LRHGuyCommented:
If it's the main form, you can use:

Application.ShowMainForm:=false;
0
 
barnarpAuthor Commented:
it is the main form, but when I use Application.ShowMainForm:=false; in the Formcreate procedure, it still runs the FormShow procedure.

Code:

procedure TfrmMain.FormCreate(Sender: TObject);
begin
  if (paramstr( 7 ) = '') then
      begin
      Messagedlg('Please select a valid number.', mtError,[mbOK],0 );
      Application.Terminate;
      Application.ShowMainForm:=false;
      Application.ProcessMessages;
      Exit;
      end;

Still goes into Formshow.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
kretzschmarCommented:
why not place your check into the project-source like

...
  Application.Initialize;
  if (paramstr( 7 ) <> '') then
  begin
      Messagedlg('Please select a valid number.', mtError,[mbOK],0 );
     Application.CreateForm(TForm1, Form1);
     Application.Run;
  end;
...

just from head

meikl ;-)
0
 
LRHGuyCommented:
The problem may be elsewhere...I tried your code and it works as expected here. The dialog pops up, and then the application ends. I also found I didn't need the "processmessages" call.
0
 
kretzschmarCommented:
ehm sorry,
should be

...
  Application.Initialize;
  if (paramstr( 7 ) <> '') then
  begin
     Application.CreateForm(TForm1, Form1);
     Application.Run;
  end
  else
      Messagedlg('Please select a valid number.', mtError,[mbOK],0 );
...

meikl ;-)
0
 
barnarpAuthor Commented:
Thanks for the comments. I also suspect that the problem could be elsewhere. kretzschmar , I tried your solution and it worked 100%.
0
 
kretzschmarCommented:
>I tried your solution and it worked 100%.
well, nice to read :-))

if you come to the grading i recommend to split the points between me and
LRHGuy, because his suggestions should be also work.

in case, if you find the problem, so that LRHGuy suggestion will work,
and u use it also, then LRHGuy deserves all points, of course

meikl ;-)
0
 
ISGDudeCommented:
I have used this in the project unit.  If a parameter is sent the form does not display.

If paramcount <> 0 then  Application.CreateForm(TForm1, Form1);

If a parameter is sent I then process them inside the formcreate event.

If you need to read values off of the form then the form will have to be visible.  I have set the width and height for the form to 0 and placed the form in the top left coner of the screen.  It will flash in the top corner as it processes it's data before closing.  I found this better than having the form pop-up in the middle before closing.

Randy
0
 
bpanaCommented:
>> >I tried your solution and it worked 100%.
:))

declare a public variable in your main form (example - gboolOK: boolean;)
in the form create event set this variable to True or False.

in the dpr:

  Application.Initialize;
  Application.CreateForm(TForm1, Form1);
  if Form1.gboolOK then
    Application.Run
  else
    Form1.Free;

but maybe you have already done something like that ...
0
 
bpanaCommented:
please forget my last post .. i must be tired (i didn't see that you are checking a parameter value ...)
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 3
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now