Clicking on node locks edges?

[jdanish]

In the most recent build, if I click on a node (not even to edit, just select it), the edges all lock and won't unlock. I see a host of "Edit lock" messages in the console when this happens as well.

[benloh]

@jdanish I can't reproduce this either. Please send me the problem data files.

[jdanish]

Here you go. This is what I have been testing with since we are going to use it in an upcoming study. I will try and remember to test future things with other data files just in case it is a bad file, though.

VFOI.zip

[benloh]

Thanks. Hmm...I still can't reproduce. You probably already did this, but can you ctrl-c, do a pull, and run it again, just to make sure we're starting fresh?

[jdanish]

I tried the following and still see the issue:

1. clear cache in chrome
2. update to newest chrome
3. nvm use just in case gem-step screwed me up
4. npm ci
5. Try with a new database (create from scratch)

No luck.

Note, I should clarify that if you click on a node and then the edge it is still editable. But the edges table is faded and acts as if it is disabled or filtered out - clicking on the nodes doesn't work.

[jdanish]

Note this bug apparently goes back a while - you can see it on my server which is a few days behind:

http://167.71.174.206/graph/VFOI1/#/edit/C1-P1-7DG?admin=true

[benloh]

Oh. Edges are not locked. That locked message was a debug message that I committed by accident.

The fading is #197 and should be fixed by #199 once I implement it.

Closing.

[jdanish]

Ahh, sorry!!

---

(from my iPhone)

Joshua Danish http://www.joshuadanish.com

On Mar 21, 2022, at 6:56 PM, benloh @.***> wrote:

 Oh. Edges are not locked. That locked message was a debug message that I committed by accident.

The fading is #197 and should be fixed by #199 once I implement it.

Closing.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.