🚀 go-pugleaf

Dan <Dan@do.not.spam> wrote:
>
>> Do you have some dialogs in OnActivate or similar?
>OnActivate definitely did the trick.
>
>Thanks

Deciding whether or not to set wsMaximized WindowState at
run-time can make some weird problems when you extend your
app with some new features, like showing startup dialogs 
(licensing systems, tips of the day, etc...). This is what
I have faced with few years ago:

--- Problem 1 ---

__fastcall TForm1::TForm1(TComponent* Owner)
        : TForm(Owner)
{
   // Eg: I read Config and decided to open app maximized
   WindowState = wsMaximized;
}
void __fastcall TForm1::FormActivate(TObject *Sender)
{
   ShowMessage( "This message box mimics any dialog, eg. Licensing System" );
}

If you try the simple code (below), you'll see very weird 
visual effect.

The even more weird effect you'll see if you have a Panel
on the main form, which is aligned alClinet, and has to be
invisible during startup:


--- Problem 2 ---

__fastcall TForm1::TForm1(TComponent* Owner) // same as in Problem 1
        : TForm(Owner)
{
   WindowState = wsMaximized;
}
void __fastcall TForm1::FormActivate(TObject *Sender)
{
   Panel1->Visible = false; // aligned alClient
   ShowMessage( "This message box mimics any dialog, eg. Licensing System" );
   Panel1->Visible = true;
}

And that's the main reason I moved all dialogs to the most
unusual place, when I want to initiate the startup dialogs.
That't OnPaint() event:

void __fastcall TForm1::FormPaint(TObject *Sender)
{
   static bool HasPassedOnceOnPaint = false;
   if ( ! HasPassedOnceOnPaint )
   {
      HasPassedOnceOnPaint = true;
      ShowMessage( "This message box mimics any dialog, eg. Licensing System" );
   }
}

Then WindowState = wsMaximized assigned at run-time works well
without any issues known to me.


Best Regards,
Vladimir Stefanovic