Dan Espen wrote: > Michael Großer <michael.gros...@gmx.de> writes: >> When no WM is running, then no frames are around windows. > > Exactly. > >> Does a WM draw the frames around windows or does a >> WM instruct X to draw frames around windows? > > Is this rhetorical? You just answered your own question.
When X.org draws the frames, then X.org is the one who changes the size of windows (or creates the necessary events) as soon as the user moves a border with the mouse or with his fingers. When the WM draws the frames, then the WM is the one who changes the size of windows (or creates the necessary events) as soon as the user moves a border with the mouse or with his fingers. I asked the question to narrow down which one would really be responsible for creating the necessary events. After all what Thomas wrote, I conclude X.org must be changed to support touch screens in the future (regarding this special aspect). If this is true, then new trends like touch screens do not mean a quick death of FVWM, which I interpret as good news. The reason why I asked questions about touch screens was to detect early enough possible hazards that could endanger the whole project. Currently, it looks like "stress test passed". - Michael -
