#29 Wrong scratchpad resize policy

[Igor Bogomazov]

Hello,

The problem raises when two frames multiplexed in a scratchpad both have a discrete resizing values (e.g. terminal emulator and gvim) but with fixed borders of different size. The larger frame will be displayed OK, while another frame of a smaller size will be outlined with a black border.

Then if one hides/shows a scratchpad while the smaller frame is active, the scratchpad fits its size (shrinks) to the geometry of this currently displaying inner window. As a result this very window can be drawn without an ugly black border, though another frame most likely obtains one (due to reduced sizes) and effectively shrinks its size as well.

Every further such «hide/show» cycles will reduce the size of a scratchpad and all inner windows will be continually shrinking as well.

I've found that mplex_managed_geom() for scratchpad returns the geometry of the currently displaying window, though it probably should return the maximum geometry of all multiplexed windows.

As a quickfix of the bug I commented out the calling of «region_fitrep()» from «mplex_do_node_display()». Can you suggest a more convenient solution?

Thanks,

Igor

[Arnout Engelen]

Sounds reasonable - thanks for the detailed report.