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

Webvowl nodes edit capture event #182

Open
saravanch2018 opened this issue Nov 21, 2021 · 1 comment
Open

Webvowl nodes edit capture event #182

saravanch2018 opened this issue Nov 21, 2021 · 1 comment

Comments

@saravanch2018
Copy link

Dear Team,
While I could not find extensive documentation about the webvowl properties/methods, I had some difficulty understanding it. My team had few problems with some negative testing. A new node is added by simply clicking in the graph area with a default name say node 7. On clicking outside of the node it is immediately saved to the backend.
The developer by default uses the onblur event on the node to trap the event and execute some backend code. But I did not want that to happen. Only if the user presses enter while having focus on the currently editing node, it should be saved to the database. If user clicks outside of the graph, this should not trigger any backed logic.

In order to do that, I have tried using mouse clicks. But I am unable to differentiate between a onblur and the mouseclick in the webvowl node object. This is a problem because I allow the user to save the node to the database only on hitting enter on the currently selected node.

I request you to provide me either to the documentation of the attributes and methods of webvowl or how to differentiate between a mouseclick and an onblur using the webvowl node's attributes/methods? Any help is appreciated. Even if there is any sample link of a demo that will be great

@omarryhan
Copy link

Any luck @saravanch2018? I'm facing a similar issue.

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

No branches or pull requests

2 participants