🚀 go-pugleaf

"Rodolfo Frino" <rodolfowrvxg527u7qfrino@yahoo.com.jki> wrote in message
news:3fa1fc23$1@newsgroups.borland.com...
> I used it because Borland uses too.

And how many times have Borland's examples and documentation been proven
wrong?  Too many times.

> 1-  In the OpenDialog1Show event handler the dimensions
> of the first dialog are zero

I did not notice earlier that you were shrinking the dialog to 0 dimensions.

However, you should not just pick an arbitrary size for the new dimensions
when re-displaying the dialog later.  I ran your example, and upon
re-showing the dialog, it took up half my screen, and half of the dialog was
empty.  Very ugly.

Also, there's still no need to use FindWindow(), calling GetParent() on the
OpenDialog's Handle returns the same HWND that FindWindow() would have
found, and is a lot less error-prone to find the wrong window by accident
:-)

> Please, run the program and you will see that there is only one dialog
> visible.

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.

>     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?


Gambit