2009/9/16 Carlos R. Mafra <[email protected]> > On Wed 16.Sep'09 at 9:31:46 +0800, Paul Harris wrote: > > I finally had a few minutes to install and try out the Maximus and other > > features from Next. > > Great, I was waiting for some of the original people which were > in that "feature request" thread to say something. > > Is there a ChangeLog or a list of changes that I can go through and test?
> > Bug 1: > > I have a terminal and a gvim next to each other, as small boxes, on my > right > > screen (LCD). > > I maximus the gvim, and I notice there is an over lap of the windows of 2 > > pixels. > > The terminal overlaps the gvim by the window border pixel (black), plus 1 > > pixel of gvim's content. > > Yes, I see that too. > > > Bug 2: > > Same scenario as bug 1, same action performed. > > The gvim window extends all the way to the top and bottom of the screen > > (correct, i want that), it extends to the terminal on the left (a little > too > > much, see bug 1), but it does NOT extend all the way to the right. > > If i resize the gvim I can see the little wmaker sizes tooltip, it says > the > > window is 99x wide, when it should be around 137x wide. > > I discovered that if the small-gvim-window is 84x wide, then it will > Maximus > > to the full right side of the screen. If it is ANY LESS than 83x wide, > > then it will only maximus to 99x wide. > > Is this by design? > > From your description about 83x versus 84x, I think this bug is due > to the fact that the in the computation of the intersection lengths > I have overlooked the frame widths, which are 1 pixel wide. So > it can be that when you resize by one pixel more (or less) the > intersection will be entirely due to the windows frame widths, > and the computation will change entirely too and will be > wrong because it "missed" the widths. > > I also think that perhaps the top part of the windows may > have an additional source of imprecision due to the titlebar > height. > > If I understood your problems correctly, the above behavior > can be fixed once I know for sure the window geometry > parameters. So for example, does the coordinate frame_y of the > window also include the titlebar height and frame width or > these are later subtracted from it to put the window at > this corrected y coordinate? > > uuh, I'm not sure... I think I know where you are coming from. But the problem in Bug2 results in the window being a LOT narrower than it should be. 99x wide instead of nearly 140x wide. I don't think that is due to imprecisions around the borders etc. > > Bug 3: > > I have turned on "When maximizing - do not cover icons" (do not cover > dock > > is UNTICKED) > > I turned on "Full screen maximization" in the Window Attributes of my > GVim > > window (on a per window basis). > > When I maximise or vertical-maximise my gvim window, it will resize > > vertically until it HIDES the wmaker title bar. This is as expected. > > When i Maximus my gvim window, it will vertically resize so that it > covers > > the icons, but does NOT go bigger until the title bar is hidden. > > Again, this is due to me not knowing exactly when to add/subtract > the titlebar height from the y coordinate. I have to look at what > the other maximizations do and copy. > > Probably. To be clear, when i do NOT have "Full screen max" turned on, it will correctly resize it so that the window does not cover the icons. So you just need to adjust for the title bar when its Full Screen Max. > Bonus bug (possibly unrelated): > > The tooltip I mentioned in bug 2 appeared top left of my right screen > (same > > screen as gvim). Shouldn't it appear on the window or in the middle of > the > > window or something like that? > > Hm, what does your WPrefs configuration say for that? > But it looks unrelated to the Maximus feature. > > I shall check later, not in linux now
