Patch Context menu interaction / UI / refresh issues

Hi,

just noticed quite severe issues in 7.0 stable with the drawing/refresh and interaction when renaming and re-ordering process operations.

  1. When double-clicking in operation name to rename it, it also is stuck to the mouse position even when not dragging. In the gif you can see I don’t hold the left mouse button anymore, still the operation follows my vertical mouse position.
  2. When trying to hit escape to get out of this (it felt like the logical thing to cancel what I was doing) it only stopped the rename, the stuck re-ordering kept happening. You can see that the name popped back to its previous name correctly and the text wasn’t in “edit mode” anymore (also correct), but the other (wrong) action kept happening.
  3. I could only stop this by clicking somewhere else. You can see the UI doesn’t refresh correctly: sometimes the operation was still being drawn with an indentation. And towards the end of the gif you can see that the surrounding box to the operation name kept the width of “asdf” while it should have enough space for “Update”. Only switching the patch in the UI or expanding the input/output-ordering-menu of the Update operation helped to refresh it.

zYDxKWEU3L

1 Like

Can no longer reproduce this one. I think it was fixed around two weeks ago when addressing the pan issue we had. Can you confirm?

1 Like

The bug report was indeed also not from 7.0 stable, but 7.1 preview 0024 (released on Oct 7th).
So that’s been more than two weeks for sure.

Checked 0024 again (bug still happening right away), now checked with 0076 and the bug indeed is gone.

But I’ll take this as a chance to report the laggy feeling of reordering operations in general, see the following gif. I’d expect the dragged item to remain under the cursor, not get stuck along the way multiple times. The document recompiles when releasing the cursor, which is fine and where a lag is expected and okay. But it should not lag while the dragging is still happening I feel.

Is it ok to report here or should I open a new issue with just that?

U1xzlAAeHF

Good point, fixed in upcoming.

3 Likes