Knime 5.3 - some early comments

KNIME Analytics Platform
1

Well folks

Following last weeks 5.3 event, i finally switched to modern UI.
It has come a long way, and i now find myself working almost completely here.
well done to the team, keep it coming :smiley:

Couple of things i miss,
– Copy table with headers from results window
– select all in table (ctrl+A doesn’t seem to have the expected behaviour)

Other than that, shortcuts and new UI features making work a little faster.
Loving KAI, still early days, but it has speeded up some aspects well. The build me a workflow is still a work in progress but haven’t had much time with it yet.

btw i also noticed the Expression node was not bundled with the latest version, not sure if it was something i did, or if that is expected.

Thanks again Knime Team!

11 Likes
2

Hey @Gavin_Attard,

great to hear that you switched to modern UI!

  • Copy tables with headers is already possible by pressing ctrl + shift + c (we are still lacking documentation)
  • ctrl + a is currently missing, but we already have an internal ticket for it (internal reference UIEXT-1268)

Greetings and thanks,
Daniel

5 Likes
3

i am trying to locate the aligning (horizontal /vertical ) buttons on modern UI .can someone suggest where to find and set default.

4

The 5.3 version brought the Modern UI to the Row Filter node and deleted the option to filter by Not missing values. I know that we can filter Not Missing using a rule-based row filter or a row splitter node, but I think it’s better to not delete functionalities from nodes.

5

hi @Marthael , are you sure that it is not just that that the new dialog layout is perhaps initially less intuitive rather than lost functionality?

image
image511×807 17.8 KB

3 Likes
6

Hi takbb, you are right I didn’t notice it.

1 Like
7

ye had to double take on this one too

8

@DanielBog - One missing feature in new UI which would be great to bring back.
Drag and drop files into Spaces.

Worked in old UI, at present i have to shift he files in File Manager, then refresh then use…

9

Yeah, this option will return (internal ticket AP-23003), so you can use it in more complex predicates, where the “Filter behavior” output option does not work or is too cumbersome. Watch out for 5.3.1 and 5.4 :slight_smile:

3 Likes
10

The “Output Non-Matching Rows” workaround gets trickier when multiple conditions are combined…

1 Like
11

Very good point @iCFO

12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.