Skip to main content

[Migrated content. Thread originally posted on 14 August 2004]

I have an initial screen, calling floating windows.
On installation, the user has the choice to maximize the screens or put them on screen like the way they are programmed (800 * 600).

If the user selected the maximize-option, upon opening a screen I change the action in Action-maximize.

Is there a way that the user doesn't see the proces of maximising his screen ?

I tried to set the handle unvisible before maximising, and afterwhile, set the handle visible but what I see is that the screen is maximised, but the controls aren't.

Second question ....
you can set RLM-MOVE-X for a control, but I would like to make a suggestion.
If a control is in the middle of the form, the position has to be changed in CONTROL-OLD-COL (NEW-WINDOW-SIZE - OLD-WINDOW-SIZE)/2.

Any suggestions ?

[Migrated content. Thread originally posted on 14 August 2004]

I have an initial screen, calling floating windows.
On installation, the user has the choice to maximize the screens or put them on screen like the way they are programmed (800 * 600).

If the user selected the maximize-option, upon opening a screen I change the action in Action-maximize.

Is there a way that the user doesn't see the proces of maximising his screen ?

I tried to set the handle unvisible before maximising, and afterwhile, set the handle visible but what I see is that the screen is maximised, but the controls aren't.

Second question ....
you can set RLM-MOVE-X for a control, but I would like to make a suggestion.
If a control is in the middle of the form, the position has to be changed in CONTROL-OLD-COL (NEW-WINDOW-SIZE - OLD-WINDOW-SIZE)/2.

Any suggestions ?
Some thoughts:

You could set the window size attribute to Maximized on the Windows shortcut that starts your application (right-click on the shortcut and choose Properties - it is the "Run:" field). (Have your installer set this option when the shortcut is created.)

Or you could create a small program (in C, VB, or Acucobol) that does nothing but start your "real" program by calling the CreateProcess API call with the STARTF_USESHOWWINDOW value in the dwFlags field and SW_SHOWMAXIMIZED value in wShowWindow.

You may also be able to avoid this by using the Windows command "start /max wrun32 yourprogram.acu" but I don't know if a black console window will briefly display.
Terms & ConditionsAccessibility statement