On 13 May 2013 22:41, Dominique Michel <dominique.mic...@vtxnet.ch> wrote: > Le Mon, 13 May 2013 21:46:43 +0100, > Thomas Adam <tho...@fvwm.org> a écrit : > >> On Mon, May 13, 2013 at 09:05:41PM +0200, Dominique Michel wrote: >> > Hi, >> > >> > It is several Maximize function in Fvwm-Crystal. When a new window >> > is opened, a SetEnv made a variable with its window id and its >> > maximized state. 2 temporary files are also created, one with the >> > window width, the other with its height. I done this because I >> > found no other to do what I want and this to survive a restart. May >> > be it is simpler solution, but I didn't find it if it exist. >> >> Sounds very over-complicated to me. Using a WindowID is bad here, not >> necessarily because it's only per-window, but for the fact that when >> FVWM restarts, the inherent use of WindowStyle to set the style of >> the window means it's lost on a restart. >> >> When FVWM restarts, its windows are reparented to the root window, >> and then reparented when FVWM starts again; in your case, the >> maximized state is recorded for windows across restarts, but FVWM >> doesn't record the state of all states across restarts for >> WindowStyle'd windows. > > They are lost anyway when fvwm restarts, it is why a added a function > to restore them. The id is used only to apply the fullscreen styles on > the full screened windows.
Well that's probably half the problem then, > When working on fvwm-crystal, I restart quite often and get You're doing that wrong. See: https://plus.google.com/u/0/100692260234415059882/posts/YqzdH3jeAEg > tired of resizing the windows after a restart. Get BugOpts ExplainWindowPlacement and similar in to your logs so I can see what's happening, or better yet, get a consistent application which shows your problem, and let me have steps to reproduce it. -- Thomas Adam
