> >-------- Original Message -------- >Subject: Re: FVWM: Resizing any window to a known geometry >From: Dan Espen <des...@verizon.net> >Date: Fri, December 14, 2012 11:07 pm >To: <msib...@crosswire.com> >Cc: fvwm@fvwm.org > > ><msib...@crosswire.com> writes: > >> So I am taking your answer to mean: "FVWM can't move a >> window by handing it an X11 formatted geometry string" >> >> Any particular reason for this void? > >Void? > >Fvwm can't support dozens of different command formats. >To convert a geometry string write a program that does the conversion >and generates the command(s) you want. > >Then do something like: > >PipeRead 'MyConverter 800x600+10+10' > > >Please don't top post. > >-- > >Dan Espen
Howdy, It isn't that FVWM doesn't support it, but rather that FVWM doesn't 'export' it. Right? FVWM runs on top of X11, which itself uses a standard geometry format. But FVWM reinvents the wheel instead of providing a hook into the lower layer. There are a dozen or more application that take the above format on the CLI, including FvwmIconBox I believe, which takes the format as a Style argument. Surprising that FVWM itself, doesn't conform. Feature request? Call the Command MoveX of something? My guess is that the Move, Resize commands already use this format before it punts the request to X. It's probably less than a 50 line patch. I would do it myself, but my C sucks. The PipeRead solution is not a good one. The example above is simplified. If FVWM can take an X11 formatted string, I can get such strings from commonly available libs, and push them with FvwmCommand. I have considered alternatives, and in this case, all other alternatives suck more. So the question is: Can I communicate with FVWM using a standardized format, or do I have to kludge something up? Generally, it is preferable to do IPC with standardized formats. Since the core advantage of FVWM is its ability to do simple IPC with user developed tools, I figured it would be appropriate to ask if the FVWM team would be interested in implementing such a feature if it does not exist. So... Can the FVWM take X11 formatted geometry strings natively? Please, please please? It is Christmas :-) Thanks in advance!
