🚀 go-pugleaf

> My screen still flickers when I run your code.  Whatever window is
currently
> on top (including the desktop itself in case everything is minimized) when
> the dialog is displayed, it is repainted in full upon displaying the
dialog.
> I'm still sticking with my earlier example, for a few extra lines of code
it
> produced a cleaner effect for the user.

I know that there is a little bit a flickering I mentioned it in my previous
post.
I didn't say that the example is perfect :-)

 > >     OpenDialog1  = new TOpenDialog(this);
>
> I am wondering, why do you keep showing examples that dynamically create
> everything at runtime instead of using the form designer at designtime?

There are several reasons. One of them is that, in general, the user can see
exactly all the components
on the form and their properties without posting extra files. Never develop
any form at design time.
Do everything at runtime is less error-prone. Imagine that you develop a
complex mainform at designtime.
Then, one day you open the project and by mistake you change the value of
some properties in your Object
Inspector without realizing. Then you recompile your project and now your
program has got different values
for one or more properties and your program runs but does not behave the way
you intended to.
If you design each and every form at runtime these type of error will never
take effect, since your
program will set the properties at runtime, overriding any values entered in
the Object Inspector by accident.



"Computers are machines that make us think that they could think one
unthinkable day"
Rodolfo, 2003