From: thefadden@gmail.com   
      
   Once upon a time, Windows remembered the last position and size of the main   
   CiderPress window.  This apparently changed some time ago, and Windows now   
   uses a default behavior that tries to make the window cover most of the   
   current display.   
      
   This is annoying, but a little hard to work around with the way the program is   
   currently structured.  I tweaked it to make the window 1150x800.  I didn't   
   limit it based on the display metrics, on the assumption that nobody runs at   
   1024x768 anymore,    
   though this might be a bad assumption for virtual machines.  I figured I'd try   
   this and see if it was a problem for anyone.   
      
   A full solution would use the more modern window placement code, which   
   correctly handles situations with multiple monitors.  (If you just blindly   
   save and restore the previous position and size, you can have some unpleasant   
   surprises if displays have    
   been removed from a multi-monitor system.)  I use this in SourceGen and it   
   seems to work well.   
      
   Right now CiderPress reads its settings from the Registry, and does so after   
   the window placement is already determined, so it's a little awkward to   
   restore the window metrics.  My goal is to stop using the Registry to hold   
   settings, which will make    
   various things simpler, but requires rearranging some code.  Because this will   
   require some OS-specific testing, this will likely be the point where I drop   
   support for WinXP.  Doing so will reduce the size of the distribution   
   dramatically since I won't    
   have to pack in the MFC-for-WinXP compatibility DLLs, and I can stop using the   
   VS2013 tools for builds.   
      
   cf. https://github.com/fadden/ciderpress/issues/41   
      
   Release: https://github.com/fadden/ciderpress/releases/tag/v4.0.5-d2   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)