Re: Toggle horizontal/vertical maximize behaviour
Chris Burkhardt <chris-y5F6wxj2E/[email protected]>
| Newsgroups | gmane.comp.window-managers.ion.general |
|---|---|
| Message-ID | <[email protected]> |
Tuomo Valkonen wrote: > On 2009-01-02, Chris Burkhardt <chris-y5F6wxj2E/[email protected]> wrote: >> 4) Again in the top frame do a 'Mod1-K S' to do a horizontal split. >> 5) In one of the top frames do a 'Mod1-K V' to collapse the bottom frame. Then >> 'Mod1-TAB' to the other top frame and 'Mod1-K V'... the bottom frame >> unexpectedly stays at 0! > > Ah... well I'd classify that as an (unintentional) feature then. > Maximise is completely unaware of tiling/layout, it just works on > a per-frame basis. Ah, I see. But what I think is still a bug is that after performing a 'Mod1-K V' in the other top frame (as in step 5 in my example), then the originally maximized frame forgets its original height. 'Mod1-TAB'ing to it and trying to un-maximize it with 'Mod1-K V' has no effect, although even with the intended per-frame maximize I would expect it to (right?). Also, resizing ('Mod1-R') in the bottom frame has no effect at this point, it is stuck at 0 height. > It should be done somewhat differently (snapshotting > entire layout instead of just saving the size of a single frame) for > what you want to work. Yes, that's what I really want. Hopefully it will annoy me enough that I'll finally take a little time to learn enough of the Ion3plus code that I can turn out a patch that's at least good enough for my purposes. Thanks for everything, I hope your PhD defense/preparations went (are going) well for you. - Chris Burkhardt