Leron Gray

I have a solution, I think. I'm new to frontend stuff so please correct me if my understanding or terminology is wrong. I've been having this same issue of nodes...

@manishpatelUK Hi, the most important thing was the wrap any changes or methods called from the cy instance in a nextTick() block.

Hi, could you try this proposed solution? https://github.com/rcarcasses/vue-cytoscape/issues/57#issuecomment-684045652

This is definitely an issue, but I found that this particular cause is the cxtmenu (which you've misspelled as "cxmenu" by the way). If you check the console output, you...

I just tried implementing `if (!cytoscape("core", "cxtmenu"))` and it similarly seems to work only when putting the cxtmenu in the conditional similar to the code I posted above. So maybe...

You can do that with the same cytoscape syntax as the regular cytoscape.js. https://js.cytoscape.org/#selectors Here's an example where I change the node image based on a node property, as well...

@lateralusd Thanks for putting together a package. Any chance you'd update bindings to the newest version of Frida? Doesn't work in v15/16 because some of the API changes and your...

Ay, this funny AF.

I was able to solve this by just adding `mingw64\bin` and `nim-1.6.X\bin` to my PATH. This just means that every nim update done through `choosenim` would need another PATH change.

@realboa Do you mean something like this?  If so, this is in the Cytoscape.js documentation. In the Cytoscape.js [documentation for labels](http://js.cytoscape.org/#style/labels). You just set `label` to a value like...