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
Remember column was resized in a data table and apply resizing on column width computation?
Actual behavior
I'd like to retain column width in data tables across Orange. For example, I open Data Table and resize one text column. Now, I change something upstream. The data table is updated and column resized to default. If I wish to interactively observe changes to my workflow, I have to keep resizing the column to the desired width.
Steps to reproduce the behavior
Corpus (deerwester) - Statistics - Data Table. Resize column in Data Table, recompute statistics.
Additional info (worksheets, data, screenshots, ...)
This might be a pain in the butt to do. Or not. I rely on experts (@ales-erjavec) to decide whether this is a doable solution.
The text was updated successfully, but these errors were encountered:
However, after discussing with @janezd, we concluded it would be nice to have a mixin, that could be used in widgets such as Test and Score and Predictions. Moreover, it would be nice to have a hint, that would remember the column name (if I resize Title, Title would be resized, even if the order of the columns is changed).
Orange version
3.36
Expected behavior
Remember column was resized in a data table and apply resizing on column width computation?
Actual behavior
I'd like to retain column width in data tables across Orange. For example, I open Data Table and resize one text column. Now, I change something upstream. The data table is updated and column resized to default. If I wish to interactively observe changes to my workflow, I have to keep resizing the column to the desired width.
Steps to reproduce the behavior
Corpus (deerwester) - Statistics - Data Table. Resize column in Data Table, recompute statistics.
Additional info (worksheets, data, screenshots, ...)
This might be a pain in the butt to do. Or not. I rely on experts (@ales-erjavec) to decide whether this is a doable solution.
The text was updated successfully, but these errors were encountered: