Interactive Views Not Opening in Separate Tabs in KNIME 5.4

Hello, I have updated to version 5.4, and now, when I open interactive views, they do not open in separate tabs in KNIME. This prevents me from keeping the interactive views open while minimizing the KNIME window with the workflow. However, if instead of opening an interactive view, I open the table view, it does open in a new tab, allowing me to have table views open while minimizing KNIME.

Is it not possible for interactive views to open in new tabs? In previous versions before 5.4, they would open in separate tabs. Is there a way to configure version 5.4 so that interactive views open in new tabs?

thanks!

Hi @Pablo

If you have an interactive node, make sure to have the View window open. From there, you can click on Open in new window.

If this option is not there then I’d say it’s embedded.

2 Likes

Thank you very much, but that’s not the issue. The interactive view does open in a new window, but I’m not sure if I’m explaining myself clearly. With KNIME 5.4, the window opens within the same workspace, whereas with KNIME 5.3, it opened in a completely separate window.

Here you can see how in KNIME 5.3 the interactive view (tab on the right) is independent of the main KNIME program window. This allows having multiple interactive views open while the main KNIME window is minimized. This was very useful for me when working with multiple screens, as I could have the KNIME views on one screen while minimizing the KNIME program and still keep the interactive views visible on the other screen.

knime 5.3:

image

On the other hand, when switching to KNIME 5.4, even though the interactive views open in separate windows, they are grouped within the KNIME program tab. This prevents me from minimizing the workflow window without also minimizing the interactive views, which is not ideal for my workflow.

The interactive view is open but “anchored” to the KNIME program window. I’ve been looking through KNIME’s settings, but I haven’t found anything that could configure this behavior. I understand this is likely a feature of the new 5.4 version. I’m not sure if there’s a way to revert to the 5.3 behavior in this regard.

thanks!