View Single Post
Old 10-01-2022, 08:49 AM   #8
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,749
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by chaley View Post
The questions I asked before are still unanswered. Kiwidude will run into the same problems.

It shrinks the column to the size of the viewport less a few pixels.
Took me a moment to figure out how to make a column wider than the viewport - make it wide, then shrink window


Quote:
Originally Posted by chaley View Post
The second one isn't clear. What is supposed to happen?

Are the columns reduced in proportion? To a fixed size equal to the window size / number of columns? With a minimum size, and if so, what size? What happens if the sum of the minimum sizes doesn't fit in the window? Is this actually a useful function?
The goal is to reduce need for (even eliminate) horizontal scrolling, and having to manipulate the column header bar with the mouse. I'll use characters as the illustrative unit.

Widest column is shrunk (in 2 char bites) until all columns are visible, or are at minimum width. So if col-a was at 80 chars, and col-d was 61 chars, col-a would be shrunk until it was 60 then col-d would be shrunk to 59, then col-a to 58 and so-forth-and-so-on.

BR
BetterRed is online now   Reply With Quote