-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FP-2468 - Study performance decrease in tree view flow editor #166
FP-2468 - Study performance decrease in tree view flow editor #166
Conversation
quirinpa
commented
Jul 10, 2023
- FP-2468 - Study performance decrease in tree view flow editor
a95e770
to
db6808e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be fair I saw a couple of improvements, ie: when selecting node and then selecting another node, there's no longer a 300ms delay (which is very good, even though it wasn't noticeable by most humans). This, just to say that the idea of the PR seems good and the direction seems interesting.
The issue is, I made a couple of comments, to be honest most of them aren't that big of a deal. But upon testing the PR thoroughly I found a lot of regressions that need to be addressed before merging this.
List of regressions that I've found (which doesn't mean more might have slipped):
-
After dragging a selection of nodes, or a selected node it gets de-selected in the end.
-
Double clicking a subflow, doesn't open said subflow (infinite loading).
-
Double clicking the start node in tree view, causes Add Node Bookmark to forever disappear.
-
Selecting a node, or multiple nodes, causes it/them to be dragged along side with another node that you want to drag.
As I said, there might be a lot more regression issues I didn't catch.
- [Part of comment](#166 (review))
b88f73e
to
47a05b4
Compare
This is not happening to me. It may be a (older) problem that happens sometimes in which the flow fails to load due to a timeout. Can you please test again and see if it still happens? |
This is fixed. |
This problem was already in dev. This PR fixes it: |
Not anymore ;) |
Fixed |
f81ed83
to
a946b18
Compare
a946b18
to
d5ae392
Compare
You're right. I can confirm that, and already have a fix here. |
I could replicate this 100%. As in, if I open the flow from the Explorer, it opens fine, but when I try to open it from inside the flow it will happen 100%. Also, tested in 2.4.0-4 and it worked fine (to be fair didn't test in dev yet to check if it isn't caused by this PR). |
Ok. Thank you. I didn't realize you were trying to fix that in that PR. Can you rebase or merge with dev? It has been updated. |
d5ae392
to
c1fde12
Compare
Kudos, SonarCloud Quality Gate passed! |
1399d59
to
ebdd446
Compare
Wouldn't happen this way |