Skip to content
This repository has been archived by the owner on Jul 29, 2019. It is now read-only.

Vis + Vue, when addNode all nodes are affected by the last added node #3142

Closed
DanielWLam opened this issue Jun 7, 2017 · 10 comments
Closed

Comments

@DanielWLam
Copy link

DanielWLam commented Jun 7, 2017

When I add a node, I expect it's label should be unique, however, when working with vue and Vis(version >= 4.19.1), all the nodes's label would be changed to the last added node's label. Here is an example:
https://jsfiddle.net/348d58jc/1/
It's weired.
But when I search the old issue, I find out this jifiddle didn't have such problem... As you can see, all the node has its own label:
https://jsfiddle.net/8u84ud3s/

@wimrijnders
Copy link
Contributor

I'm sorry, I don't see this happening in the first jsfiddle, it appears to be working as expected.

Exactly what should I do in the example to get the behavior you report? Perhaps I have to do something special.

@DanielWLam
Copy link
Author

DanielWLam commented Jun 7, 2017

Well, please try to click the ADD NODE button more than twice, and you should see those added node's label become the same. As expected, each node's label should be a random number @wimrijnders

@wimrijnders
Copy link
Contributor

Aaah, ok. It's the labels of the new nodes that show this behavior. Thanks for the explanation.

@DanielWLam
Copy link
Author

How can I resolve this problem? Turns out that v4.17.0 dosen't have this problem @wimrijnders

@wimrijnders
Copy link
Contributor

@DanielWLam To answer that, I'll have to investigate how it happens. I ask for your patience, this is one of many things I need to do.

@wimrijnders
Copy link
Contributor

@DanielWLam In your opinion, is this issue by any chance a duplicate of #2567?

@DanielWLam
Copy link
Author

@wimrijnders umm.. maybe these two issues are caused by the same problem, though they are not exactly the same. I solved it with the solution mentioned in #2567 . However, I hope it could be fixed as soon as possible.

@wimrijnders
Copy link
Contributor

@DanielWLam I've found the root problem for this; please see the discussion in #2567 for explanation.

@wimrijnders
Copy link
Contributor

wimrijnders commented Jun 9, 2017

Duplicate of #2567.

@DanielWLam
Copy link
Author

Thank you very much! @wimrijnders

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants