Make CanvasGroup node that's compatible with Controls

[markdibarry]

Node2Ds aren't the only ones that suffer from the individual draw call opacity issue. Is there a reason why CanvasGroup node is Node2D only? If having two separate versions is too tedious, is there a reason why this can't be implemented as part of CanvasItem?

[phnix-dev]

Also, the CanvasGroup node works with Control children. (e.g. with a TextureRect node)
Does anyone know how to implement the shader code from the CanvasGroup documentation on a Control node?

[Megalukes]

Any updates or solutions about this? You can actually use canvas groups but this will bug the size/position inheritance from parent control nodes

If I do something like the image above, it works perfectly when it comes to opacity, but it doesn't respect BaseContainer's size/position constraints. Any help would be appreciate it!

[phnix-dev]

Unfortunately, you might have to recreate the behavior with shader code or modify the engine to make a copy of the canvas group class and inherit it to the control node (this would mean creating a new c++ container node using the canvas group code, but I do not know if it can work).

[tsutsen]

I've made a GDExtension to solve this issue: https://github.com/tsutsen/CanvasGroupContainer. It adds a CanvasGroupContainer node that renders like a CanvasGroup but iherits all the nice layout feature from Control. And here's the proposal: #13338

[Mickeon]

For the sake of linking, here's godotengine/godot#111380

[gusg21]

Would also be great to have mouse_entered and mouse_exited events aggregated for CanvasGroups on Controls, useful for buttons over buttons, etc.!