You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following below draft spec by @dsmmcken
- **Resize Column**: If the column is currently manually sized, switch
it to auto-resize, and reset the max column width seen to only what's in
the current viewport (NOT the max ever seen, but the actual max visible
in current viewport). If the column is currently auto sized, set the
column to manual and size to max column width seen in the current
viewport.
- The assumption that can be made is that whatever the current behaviour
is, it’s not what the users wants, so no need to require the user to
make a conscious choice between auto and resize, just present one option
to resize, and do the opposite of what we are doing currently.
- **Resize All Columns**: Same behaviour as above but apply across all
columns, and treat like an indeterminate checkbox. If any are manual,
resize all as above, but flip all to manual. If all are manual, resize
and flip all to auto.
- We should try this and see if it feels natural.
Fixed an issue where double clicking the column separator in the header
bar resizes the column without changing the column to auto resize.
- There is now a discrepancy between double clicking the column
separator in the header bar and clicking "Resize Column", as the former
auto-resizes to the largest cached width, whilst the latter resizes to
the width of content in the current viewport.
- I assume double clicking the column separator follows the behaviour of
Excel so this discrepancy is intended.
Below is a useful snippet for testing, that creates a table that has two
columns that continuously gets bigger
```
from deephaven import time_table
tt = time_table("PT0.5s").update(["x=`a`.repeat(i)", "y=`b`.repeat(i)"])
```
Closes#1486
0 commit comments