Carlo Hermus
MDI Main/Child January 04, 2009 03:49AM |
Jimbo
Re: MDI Main/Child January 04, 2009 07:45AM |
Moderator |
Carlo Hermus
Re: MDI Main/Child January 04, 2009 12:58PM |
Jimbo
Re: MDI Main/Child January 04, 2009 04:34PM |
Moderator |
Carlo Hermus
Re: MDI Main/Child January 04, 2009 07:11PM |
Jimbo
Re: MDI Main/Child January 04, 2009 07:29PM |
Moderator |
Carlo Hermus
Re: MDI Main/Child January 05, 2009 02:52AM |
Jimbo
Re: MDI Main/Child January 05, 2009 11:22AM |
Moderator |
Carlo Hermus
Re: MDI Main/Child January 05, 2009 01:09PM |
Don't know, only been using it since v12.Quote
Jimbo
Hi Carlo,
I had major problems with the sizes of internal Windows in order to get them into the proper frame. Maybe, it's better now.
Don't know what you mean by this, but I have no problems with the application performance.Quote
I had to stack all of the windows on top of each other and opening the program have shown considerable delay because of initialization of all of the windows.
Mmmm I thought this was just the way it is.. Not as a limit.Quote
Anyway, if all of the problems are solved nowadays, limitations still are here (from WD-help):
- The names and the parameters of the functions called must be identical.
My controls have the same name, this doesn't bug me.Quote
- If a control found in the internal window is directly used from outside, a control with the same name must be found in the new internal window.
I pass parameters and use classes.Quote
- The values of the global variables for the former internal window are lost.
- The persistent values of the former internal window are saved and restored in the new one.