-
Notifications
You must be signed in to change notification settings - Fork 18
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
Fix cloning pinned nodes #364
Conversation
Hrm, I don't think |
It's being called from |
Yeah - just tested this: this.resizable = !this.pinned Works perfectly. |
Amusingly, the preceding comment was better than the code. litegraph.js/src/LGraphNode.ts Line 572 in a0b06c1
|
If in future pin were to have some additional logic, e.g. pin to the top of the stack, would it not be better to have the logic for pin in the pin method, rather than duplicated? |
It would be better to actually serialise and deserialise any additional *state, no? |
I don't think so, as if new functionality is added to pin that shouldn't rely on the state of the serialized graph |
Is that a good reason to have the code work that way right now? The code should really just.. do what it's designed to do. afaik it was never designed to call But I just spent 20mins trying to ensure I didn't come across as argumentative. So if you're set on this, I won't butt in further! =P |
Pin node
right click -> clone -> crash
or copy/paste -> crash