Skip to content
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

Graph Editor - Visualization Problem when switching Schema-Graph #452

Closed
santo-it opened this issue Feb 17, 2017 · 4 comments
Closed

Graph Editor - Visualization Problem when switching Schema-Graph #452

santo-it opened this issue Feb 17, 2017 · 4 comments
Assignees
Milestone

Comments

@santo-it
Copy link

under certain conditions, n--m queries are not visualized correctly

@santo-it santo-it added this to the 2.2.x (next hotfix) milestone Feb 17, 2017
wolf4ood added a commit that referenced this issue Feb 20, 2017
- Implemented #428
wolf4ood added a commit that referenced this issue Feb 20, 2017
- Implemented #428
@wolf4ood
Copy link
Member

Fixed

@santo-it
Copy link
Author

santo-it commented Feb 24, 2017

Enrico, sorry, I am reopening this

I am still able to reproduce using latest snapshot, even if it is not easy. Below a possible sequence:

using the new demoDb (but problem appeared also with beer db if you remember)

anonymous users on chrome, if it makes any difference:

enrico2

@santo-it santo-it reopened this Feb 24, 2017
@santo-it santo-it changed the title Graph Editor - Visualization Problem - Match Graph Editor - Visualization Problem when switching Schema-Graph Feb 24, 2017
@wolf4ood
Copy link
Member

hi @santo-it

this is a different issue. The previous one fired a JS error. I think this one not.
I bet if you fire again the query, it will adjust the rendering.
It should be caused by the first rendering optimization in the first load.

wolf4ood added a commit that referenced this issue Feb 24, 2017
wolf4ood added a commit that referenced this issue Feb 24, 2017
@wolf4ood
Copy link
Member

Fixed also this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants