GNU bug report logs -
#14233
24.3; Don't constrain frame size to character multiples
Previous Next
Reported by: E Sabof <esabof <at> gmail.com>
Date: Sat, 20 Apr 2013 00:04:02 UTC
Severity: wishlist
Found in version 24.3
Done: martin rudalics <rudalics <at> gmx.at>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Hello.
25 apr 2013 kl. 09:31 skrev martin rudalics <rudalics <at> gmx.at>:
> > I don't see how. The problem is what to do with leftover pixels when
> > the removed element isn't a multiple of the character size. Measuring
> > the frame in pixels does not help when removing, for example, a tool
> > bar that is 1.5 character high. It is the same problem, what to do
> > with 0.5 character height. Now if windows are measured in pixels, we
> > can give those pixels to windows, but frames measured in pixels does
> > not help.
>
> Maybe we are just miscommunicating. IIUC the above scenario is of
> interest only with an "external" element on a tiled/fullscreen/maximized
> frame (if the frame is not of that kind we just remove the external
> element).
If the goal is to not resize the frame, removing an external element will always mean there are leftover pixels.
So the scenario always apply.
>
> If you agree on that, we have to find out what to do with the leftover
> pixels. And I earlier said that "you" should pass these leftover pixels
> via change_frame_size to the window resizing subsystem. This means that
> the routine that removes the element has to (1) calculate the number of
> pixels occupied by it, (2) communicate the removal of the element to the
> window manager, if necessary, and (3) add the number of pixels of the
> element to the number of pixels occupied by the frame's text size and
> call change_frame_size with the new value. What am I missing?
Jan D.
This bug report was last modified 10 years and 154 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.