From: Jonatan L. <th...@ho...> - 2004-06-19 20:19:11
|
On Sat, 19 Jun 2004 20:47:09 +0100 squidge <bu...@er...> wrote: > > Please run "xprop WM_NORMAL_HINTS" in a shell, click such a tiny > > window, and mail the output. > > > > /Jonatan - [ http://kymatica.com ] > > Ah! All is reavealed (as below) > > WM_NORMAL_HINTS(WM_SIZE_HINTS): > user specified location: 515, 422 > program specified location: 515, 422 > user specified size: 361 by 141 > program specified size: 361 by 141 > program specified minimum size: 361 by 141 > program specified maximum size: 0 by 0 > window gravity: NorthWest > > That's a very handy little command isn't it? Clearly the program > shouldn't set a maximum size smaller than the minimum size! > > Would it be very expensive performance-wise for OroboROX to check for > this situation? No. =) It should probably not use the maximum size if it's smaller than minimum size. But I guess that setting maximum size to 0 by 0 means something special. Anyone that knows what or should I browse through the standards? Anyhow, here's a patch (attached) that might fix it. Copy tinywinfix.patch to OroboROX/src/src and go there and write "patch < tinywinfix.patch" in a shell (or the ROX-Filers shell-minibuffer), then right-click on the OroboROX icon and choose "Compile". When it's finished, double-click OroboROX and answer "Execute" on the ROX-Session dialogue to make it restart. (Assuming you have the new ROX-Session, Otherwise type "killall OroboROX" in a shell, or log out and in again...) Please report if it fixed the problem! And all you other people who had problems with tiny windows, please try this out too... /Jonatan - [ http://kymatica.com ] |