Bug: Embedded Node Config panel can become "sticky" when opened for Expressions node

Description:
When the option to use the embedded config panel is switched on, if the Expression node is selected and you attempt to reduce the width of the panel, it becomes “sticky” and enlarges and reduces with the mouse moving even though the mouse button has been released.

Steps to reproduce:

  1. Switch on “embedded node configuration dialog” in preferences
  2. Place an Expression node on the workflow
  3. Attempt to reduce the width of the the configuration panel, dragging and dropping the panel edge
  4. Move the mouse back over the workflow
  5. The panel edge moves back with the mouse and remains “stuck” to the mouse movement until another node is clicked.

Actual results:
The panel is “sticky” to the mouse and the width increases/reduces with the mouse movement.

Expected results:
The panel width should remain where it was dropped.
Attachments:

OS:
Win 10

3 Likes

Ditto here on Windows 11. Also the ability to “evaluate rows” is lost in the embedded config window making it quite a bit less useful.

2 Likes

By the way, I really miss the functionality in the classic interface that allowed freely placing these panels.

1 Like

@iCFO , Yes, I noticed though that there is an “eXpand” button (top right of the Expression config panel) to make the config full screen again for the Expressions node which I’m sure will get well-used!

1 Like

I missed that and it works nicely! At first I didn’t like the concept as we were once again restricted to only the configuration window without copy and paste access to the data and column names, but now that the Expression node supports Input and Output tables as well as copy and paste for expression building it is no longer an issue for that node. Really loving these improvements!

2 Likes

Thank you @takbb for reporting this!

There is a ticket to address fix the problem: NXT-3030

2 Likes

Internal ticket ID: NXT-3030
Summary: Fast resize of side pane has scripting editor capture mouse
Fix version(s): 5.4.1, 5.5.0

1 Like

Closing this topic as this issue has been resolved.