Hello - can you please bring the wrap column names to version 5? Or at least provide the capability to enter the number of characters a column name should have?
Thank you!
Hello - can you please bring the wrap column names to version 5? Or at least provide the capability to enter the number of characters a column name should have?
Thank you!
Hi @sw1336
You might be better off in the dedicated topic regarding feedback on V5. Itās actively monitored by the devs.
Thank you, and will doā¦
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
I think that this suggestion was missed somehow, but it is still desperately needed. The Modern UI node output window is pretty much useless for quick review since often 20+ column names in a row are truncated to show just the identical beginning charactersā¦ When you have 500+ column names from multiple sources, you need more than a few characters for meaningful descriptions.
I just have to attempt to guess at column names by the visible data entries in the table below. Please wrap the column names instead of truncating them in all of the output table views.
Column header wrap has still NOT been implemented in v5.4.0.
Seriously disappointed!! Seems a pretty fundamental requirement - but thatās only my $0.02ā¦
Dear @sw1336,
Thank you for bringing this up again.
I created a ticket for the feature you requested: UIEXT-2368
I believe your idea makes a lot of sense and will disucss it internally with our devs.
Many thanks, @armingrudd
Hey @sw1336,
Thanks for the feedback and I agree that this is an important feature.
The problem is that if you ask 10 different people about their most important feature you will get 10 more or less different answers (and great ideas, donāt get me wrong ).
With the ticket Armin created it is now on our board, but the more upvotes this topics gets the easier it is for us to prioritise this.
Greetings and thanks for your patience,
Daniel
@DanielBog - The issue is that feature was available in previous versions!! It is super annoying (to put it mildly) having the need to constantly adjust the columns. Plus, the adjusted columns donāt retain state if you go to another nodeā¦
Again, this is just my $0.02.
I agree @sw1336. The ability to visually inspect data quickly is what makes (made!) KNIME exceptional compared with other data/analytics tools Iāve used
As @DanielBog says, there are lots of āimportantā features that different people would raise as priorities but to me there are certain āmust havesā with regard to data viewing:
Being able to efficiently visually inspect the data, which includes being able to read column names in full without much manual effort.
Being able to view the actual data (so āunexpectedā space padding especially at the beginning and end of a text column can be quickly and easily identified)
Being able to scroll a large result set with no (or minimal) lag
I note that there have been improvements to the Table View node and its interaction with KNIME since 5.2ā¦ It has a facility to set Column widths to āFit content and headerā which is nice, but Iād like an additional option which is simply to āFit headerā so the titles were fully visible but still allowed truncation of the data.
The attached video shows the gradual evolution of Table View from 5.2 to 5.4. Notice in 5.2.4 you cannot see the content of Table View in the lower data panel, but that changes from KNIME 5.3.
(Sorry for the poor quality of capture, but hopefully it gives the ideaā¦)
Iād also like to see that setting for the Table View node made available as configurable ādefaultā setting for all KNIME data table viewers in Modern UI (such as the data pane). I donāt want to have to keep dropping and configuring āviewerā nodes onto workflow.
I agree mostly with word saying about new KNIME expetation ā¦ but I have to say this: there is some promise witch you made by youself and samo of them do not look like user will expected to look like, for example, new tree view. A bunch of UNCATEROGIZED nodes/extensions is still looking forward to be catetogized and we do not know why they didnāt. (sorry if this is just my only specific case configuration, as you see on a picture below).
Best
Stjepan
Thank you @ssimara for reporting this. We can reproduce the issue and will address it a.s.a.p.
Itās fixed and will be shipped with the next release.