Julien Guertault wrote: > 2012/2/25 Thomas Adam : >> On Sat, Feb 25, 2012 at 12:02:48PM +0100, Michael Großer wrote: >>> Good point: Multiple mouse pointers, for example to change the size of >>> windows with two fingers. Is this rather "easy to implement" or rather >>> "utterly impossible to implement". The answer to this question >>> could be crucial about the question if FVWM will still be "cool" >>> in the future or not. >> >> Why are you and others thinking FVWM is responsible for this? It isn't, and >> could never be: X would be, and I would hope some form of API on top of it. > > It's X's job for sure (supposing it does its job of course). But FVWM > would have to expose it to the user in some way (like the kind and > number of pointers). Suppose for instance a user would like to write a > configuration file that specifies a certain behavior when dragging a > title bar with on pointer, and a different one when dragging it with > two of them.
What piece of software draws the frames around windows? Is it X or is it a WM? When no WM is running, then no frames are around windows. Does a WM draw the frames around windows or does a WM instruct X to draw frames around windows?
