home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   OS2      Fidonet International OS/2 Conference      3,371 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,192 of 3,371   
   MrG to All   
   Re: OS2 CMD window positioning   
   20 Feb 11 11:07:04   
   
   oglegroups.com>   
   a17d0828   
   GMT)   
   posting-account=hzmWuAkAAAA2pnOSFxD-DG1p-Xq6IDrg   
   From: MrG    
      
   On Feb 20, 12:07 am, "James J. Weinkam"  wrote:   
   > MrG wrote:   
   > > Once a VIO window has been resized, each subsequent invocation of the   
   > > window is automatically put in the maximised state. Restoring down to   
   > > non-maximised does absolutely nothing unless you re-maximise it, then   
   > > it will shoot the window to the top left of the screen. Restore down   
   > > again and the window returns to the position you put it with the shift   
   > > +drag operation. Restore down from maximised, close the window then re-   
   > > open it, it will open again in the maximised state. Restoring down   
   > > each time you open a window is a bit tedious besides it does nothing   
   > > for the position of the window when re-appearing from a PM app.   
   >   
   > That's not what happens here.   
   >   
   > For example if I open an eCS command prompt window, it opens in maximized   
   state at the position   
   > where all initially maximized VIO windows open and its size is 80x25. If I   
   execute mode 100 50, the   
   > upper left corner stays in place, the window grows to 100x50, and there no   
   scroll bars. If I then   
   > click the restore button, the window cahges to restored state but the size   
   and location stay the   
   > same. If I then execute e d:\config.sys, then exit from e, the command   
   window reappears where it was   
   > before the command, is still in restored state and the size is 100x50 with   
   no scroll bars.   
      
   That's what is supposed to happen. Close that window in the restore   
   state, re-open it and it should re-open in the maximised state. Or,   
   while that window is open, open another instance of cmd, and the 2nd   
   cmd window should open in the maximised state while the 1st window   
   stays in the restored state, which is what I was saying. What you are   
   referring to is session specific and does not affect the default   
   behavior of a VIO window. Same with the mode cmd being session   
   specific. I was referring to changing the default size of a VIO window   
   which the values of are stored in os2.ini I think. Mode does not   
   change the default size of a VIO window.   
   Sorry for any confusion.   
      
   --- Internet Rex 2.31   
    * Origin: http://groups.google.com (1:261/20.999)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca