[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RP] resizepct
From: |
Martin Samuelsson |
Subject: |
Re: [RP] resizepct |
Date: |
Sun, 17 Apr 2005 00:38:03 +0200 |
User-agent: |
Mutt/1.5.6+20040907i |
On Fri, Apr 15, 2005 at 10:33:54AM -0400, Mike O'Connor wrote:
> Actually, upon thinging about this further, I realized that my method is
> doing something slightly different than your proposal. Mine is assigning
> keys to resize a frame to the amount of space available to that frame
> using the already built in get_max_size function, which is possibly different
> then then screen size. (if you have a complex frame layout).
> Having said that, and having played with it in such complex frame layouts, I
> realize, I might have some bugs to work out.
With complex frame layouts ratpoison has bugs itself. The whole concept
was more implemented because screen compability than for any strong
demand I would say. The fact that rp extended splitting to work in both
horizontal and vertical introduced problems that has not yet been dealt
with.
Have a look at the threads starting with these message id:s
address@hidden
address@hidden
Probably that bug is hunted down and fixed best by someone who actually
uses frames, feel free to take the hint. ;)
However this was really about implementing resizepct with external
scripts. A proof of concept is attached. It could be optimized a bit, but
I guess this isn't what you want anyway, since there actually is no easy
way to get ratpoison to tell how big the current frame could get. At
first I though you could parse the full output of :fdump, but there's no
way you can tell from it which frames that share the same area, can you?
Maybe it would be an idea to add a command to give that information?
Than could resizepct and other users similar desired functions be
written as autonomous pieces of code that bothers no one but those who
wants them.
--
/Martin
pro2pix
Description: Text document
resizepct
Description: Text document