feature request: multiple selector/command sets about cytoscape.js-cxtmenu HOT 6 CLOSED

sorry didn't mean to close it

from cytoscape.js-cxtmenu.

commands can be function( node ){ return [ /* ... */ ]; } so the commands can be dynamic. You don't have to use the selector to differentiate elements: selector could be node, edge and commands() could specify everything.

from cytoscape.js-cxtmenu.

I definitely see the use in that and even how it can be used to accomplish this to some extent. But now if I want all the nodes with a certain class to have a cxtmenu but not the others, would I just return an empty array from the commands function for those without the class? What if I want a single node to have a menu and none others, does the command function need to run for each node? Feel free to close this, I understand how to solve my immediate situation given your advice. Thank you for this and this awesome library! Lots of fun to work with.

from cytoscape.js-cxtmenu.

You can use both the commands function and a selector if you like.

You can alternatively use enabled per command. This was missed in the readme. This is usually the best solution, because you maintain the user's muscle memory.

from cytoscape.js-cxtmenu.

from cytoscape.js-cxtmenu.

I just want to point out, that the following code works,

ctxMenuRef.current = cyRef.current.cxtmenu({
     selector: 'node, edge', // or '*'
     commands: (nodeOrEdge) => {
          if (nodeOrEdge.isNode()) {
               // do something with node
          } else if (nodeOrEdge.isEdge()) {
               // do something with edge
          }
     }
})

and this works,

ctxMenuRef.current = cyRef.current.cxtmenu({
     selector: 'core',
     commands: (coreElement) => {
          // do something with core
     }
})

but this does not work,

ctxMenuRef.current = cyRef.current.cxtmenu({
     selector: 'node, edge, core', // <-- core is never triggered in this case
     commands: (nodeOrEdgeOrCore) => { . . . }
})

from cytoscape.js-cxtmenu.