Window definitions

[omni]

Roger,

When opening a window from the menu, we can use (and do on just a couple of programs) row 0-.99 (for example, we may have to fit a button at .25 on a crowded screen for a user).

We have discovered if we want to open this window after initial entry (as a child window, or a secondary window after destroying the dialog), the top is gone, or it appears to not allow anything below row 1.

Is there a different definition that does not allow this? This has come up because in changing to buttonxp we had a few programs that have one window with some minor entry (such as selecting a key to the file), then it destroys only the objects, keeps the dialog open and displays the main window, same size, etc. The new buttons are invisible until you scroll across them with a mouse, so pretty much unusable. We have fixed these easily in every case by destroying the dialog. But in this one very large program, the space issue has come up. Destroying the dialog makes the main window display differently due to cutting off the top.

Hope that is not too confusing. Main question is just the rules for a child window size,etc.

Thanks

Fred
Omni

[omni]

I meant above row 1. Not important, just interesting. I moved all the pushbuttons down one row and its fine. It only impacted a single program..
Fred