yetanotherbot 4 Share Posted April 3, 2020 I've noticed that it's possible to end up with multiple AbstractWebNode sharing the same node ID. This causes some interesting side effects. For example, tearing down custom nodes with clearCustomNodes() can also delete standard nodes without warning. A client restart is required to restore the original web. It happens when a node is added too close to an existing node (specifically less than 5 tiles). I've implemented a proximity check as a workaround. Is this a bug or by design? Couldn't find any reference in the docs. Thanks Link to comment Share on other sites More sharing options...
Nuclear Nezz 1956 Share Posted April 3, 2020 I don't think that should happen, no. I'll take a look at it this weekend if I can. Thanks for the report! Especially where you specify that it's less than 5 tiles, that's really helpful for me to go look into the bug. I appreciate that. yetanotherbot 1 Link to comment Share on other sites More sharing options...
yetanotherbot 4 Author Share Posted April 3, 2020 Thanks Nezz! Appreciate it. If it doesn't reproduce easily let me know and I'll put together a code sample. Link to comment Share on other sites More sharing options...
Nuclear Nezz 1956 Share Posted April 11, 2020 On 4/3/2020 at 10:55 AM, yetanotherbot said: Thanks Nezz! Appreciate it. If it doesn't reproduce easily let me know and I'll put together a code sample. I'm going to add in some synchronization checks on the add/remove methods, maybe there's just a problem concurrency. It'll be in the next release, though I'm not sure when that release is going to be at the moment. yetanotherbot 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now