atlasan

Having broken data is a situation in the-middle. Should we inform or not when we find a link with broken data? The comment seems to have copied from another section...

Hi there! Better to wait Javi's answer but here's an advice: I would include only the litegraph.js file from the src folder, or customize the inclusions in the example editor...

that's not intended and complex, normally one would open that panel enter the value and press enter (or esc to close), panning and zooming could be good the check something...

could try `canvas.clear_background_color = "#FFF";` (haven't tried myself)

``` // this.setZoom( scale, [ e.localX, e.localY ] ); // this.ds.changeScale(scale, [e.clientX, e.clientY]); var rect = e.target.getBoundingClientRect(); this.setZoom( scale, [ e.clientX - rect.left, e.clientY - rect.top ] ); ``` https://github.com/jagenjo/litegraph.js/blob/0555a2f2a3df5d4657593c6d45eb192359888195/src/litegraph.js#L7016...

keymapping has to be refactored, could send a PR looking for enter code and add numberpad-enter meanwhile

Yes, that's correct, seems expensive but actually it's quick (not sure if you how would do with thousands nodes ^_^) The alternative would try to revert a single action but...

there is a property that allows changing link color based on type of data: _LGraphCanvas.link_type_colors_ changing it on mouseover would probably need a refactor of _LGraphCanvas.prototype.renderLink_ and some other

You can use the LGraphCanvas.onSearchBox callback https://github.com/jagenjo/litegraph.js/blob/0555a2f2a3df5d4657593c6d45eb192359888195/src/litegraph.js#L5405 https://github.com/jagenjo/litegraph.js/blob/0555a2f2a3df5d4657593c6d45eb192359888195/src/litegraph.js#L11903

You are correct, that's a bug, that node was added and not correctly finished up. ATM the good way to use both property and input would be to use _getInputOrProperty_...