set_window_property('WINDOW_MAIN',window_state,maximize);
sharpeApr 5 2007 — edited Apr 5 2007Hi. Having just migrated a form from 6i to 10g I'm noticing another slight difference when I use Form Developer 10g (for Windows) to run my form.
My form contains 2 Windows. One window contains the a smaller toolbar canvas at the top of the application. The other window is the main window (named 'WINDOW_MAIN') of the application and it displays most of the application's content.
We have traditionally included the following line of code in the When-New-Form-Instance trigger to maximize the amount of space we have available on the application's canvas:
set_window_property('WINDOW_MAIN',window_state,maximize);
In Forms 6i this maximized WINDOW_MAIN basically hid the window's banner giving us a bit more space on the canvas. In 10g, this code doesn't have the same affect. WINDOW_MAIN's banner is displayed regardless of the window state being set to maximized.
As a result we don't have quite the same amount of canvas to display items as we did in 6i. I basically have to display one less row of data to compensate for the window's banner.
Does anyone have a suggestion to resolve this difference? Any help would be greatly appreciated!