Double click on nodes

[kostasgrevenitis]

Double click on nodes

[AlexDM0]

What would you like it to do? Currently, double click would open a cluster if a node is a cluster. Do I understand correctly that you would like a onDoubleClick event like the onSelect event?

Regards,

Alex

[kostasgrevenitis]

Yes exactly. You understood correctly.

[AlexDM0]

We are currently undecided on what kind of interactions we would like to bind events to. This will be raised in the next project meeting. I do think it could be a useful supplement, the broader question is: what else do we want to bind events to. We will look for a consistent events model and implement it then. The implementation itself is rather easy so I would expect we can release a new version with new events around next week.

It would be very useful for us if you could provide the use case you have in mind. This might show us ways users wish to interact with the graph that we have not thought of.

[kostasgrevenitis]

In my case I have a graph that nodes are companies and shareholders.

The requirement I have from my company right now is the following:

One click on the node : Show some menu, info window etc
Double click on the node : The graph gets refreshed and the double clicked node becomes the central one, loading the appropriate data.

I managed to fake it somehow, but I would prefer something like

graph.on('dblclick', function(event, properties)
{
//do what ever you want
});

[AlexDM0]

what kind of properties would be useful in your case?

[kostasgrevenitis]

Please can you be more specific? What do you mean by the word properties? May you set an example?

[AlexDM0]

the select event returns an object:

graph.on('select', function(properties) {
// properties = {nodes: [], edges:[]}
});

On a doubleClick event, what kind of properties would be useful for you to be returned?

[kostasgrevenitis]

For sure the node object that I doubled clicked. No only its id. This will satisfy my current requirement.

Besides that, I can't think of something else right now. But everything would be welcomed 👍

[AlexDM0]

As I mentioned in #28, Edge and node objects are part of the dataset. To correctly manipulate these objects, an update to the Dataset object is required. This will trigger all listeners you may have on the data. That is why the select event returns the ids. If we would include the doubleClick event, I would imagine this would also return the id. Could you explain why this may not be sufficient?

[kostasgrevenitis]

I am not saying that it is not sufficient, but for my current case I would prefer the whole object. But if the double click returns the id it is fine for me. I am satisfied.

[AlexDM0]

This will be added in the next release. The release will be somewhere around next week. Further events are still under discussion but this one will be included. It will return the same ID object as the 'select' event due to the reasons I stated above.

[kostasgrevenitis]

I am happy and satisfied. Thank you very much. Have a nice day! 👍

[AlexDM0]

The release containing the feature you referenced will be somewhere tomorrow. Enjoy :)