once you select a flow-variable in the now “hovering” menu, it should close instead of keep floating around for that specific field and hence block/overlay other parts
Hey @fe145f9fb2a1f6b,
thanks for the feedback. Totally agree for settings that only have 1 flow var to overwrite/expose. This becomes a bit more tricky for settings with multiple flow variables.
Greetings and thanks,
Daniel
1 Like
yep, I dont know in which world someone thinks this is more accessible than the old view to select a flow var.
@DanielBog @FemkeVegel
the only “better” thing is the type-to-search
webui
classic
This particular element is not optimal yet. For all other settings where you have exactly 1 setting that you want to overwrite I still believe that this is a nice improvement as you exactly see what you are working with. In the old UI understanding which variable belongs to which settings is a challenge on its own.
Greetings,
Daniel
3 Likes
even if the dialog covers only 1 field:
you create essentially a list of 2 options that look nearly identical because the dropdown is quite subtle and both use the same placeholder text. I would call this non-intuitive because the list like structure (again, even for just one field, you have a list of 2 (Overwrite and Output)) is far less obvious than the side by side structure.
you have people using Knime that work with data. if they see a column like structure, they expect this to be all the same. the old interface essentially displays 2 columns, hence people directly know that its 2 different things (and the the dropdown menu is quite a bit more distinguished from the input field)
You’re absolutely right — this isn’t the user experience that we aim for at the moment.That said, I’d also agree that the old nested tree on a separate tab wasn’t an ideal solution either.
These long lists of fields are not the final state yet. We’re aware of the shortcomings and plan to improve this as we move forward. A more refined concept is already in the works.
1 Like