Shadowblitz16
Shadowblitz16
> @Shadowblitz16 show me what you have so far and maybe I can help. Fork it? I deleted the project, but it was really simple as I didn't know what...
this would allow encapsulation which I support however what about marking nodes as private, protected and public in the editor too? this way people can hide nodes for modding
if this was implemented I think the best way to go about it is make everything protected by default. that way people can choose what they want to expose.
I strongly disagree. Then you have a bunch of members you might not want modders to use. protected is there for the purpose of the derived object to use and...
I think something like this should be done.. ``` #allow accessing friend members in Sprite and AnimationPlayer extends Node2D friends Sprite, AnimationPlayer pub var my_public_variable pro var my_protected_variable pri var...
Too many annotations are a bad thing, it makes code ugly and unreadable. Access modifiers and things like virtual and abstract should not be annotations.
I disagree underscores could just mean they are named with underscores. it could be the naming convention for private variables
> > Too many annotations are a bad thing, ... > > This is pretty much the opposite of what modern language design has evolved to. Don't extend the language...
> I thought this was working. Not for GDExtensions. They don't load if they are not in case sensitive `addons`
> One reason why we might **not** want to use `Addons` in C# projects is that not all C# projects will _only_ use add-ons written in C#. The add-ons written...