Neon-Cat
Neon-Cat
Hi aroelke. Unfortunately, it was a minor oversight when the project was created whilst searching for a minimal impact yet notable & compilable character. As an integral part of the...
Yes, changing it would require everyone to make the change, but a search and replace for '_.' should suffice. We could look at making the change for version 3, but...
> The problem with the interference is that it happens if you annotate a class with `[SceneTree]` whether or not you actually use `_.ChildNode` to access a child node. Ah,...
Another workaround is to add var: ``` //foreach ((_, var value) in dic) foreach (var (_, value) in dic) //_ = DiscardReturn(); var _ = DiscardReturn(); ``` Not ideal, but...
Yeah, you're right. Super easy fix, just means everyone will need to make the change, hence marked as v3. Will probably make a new property called Scene (or SceneTree).
I feel like it's something that should be communicated to consumers (and perhaps voted on) before making the change. Some may prefer to leave it as is.
(Think of it as corporate trauma ;) )
Perfect! Won't even need a v3 for that (assuming default is _). Just means @aroelke will need to specify as needed, but that's better than nothing.
Thanks all. On it.
New pre-release uploaded. If all good, I think it's worth doing it as a 2.5 release