The title says it all. It would be more convenient than placing the entirety of your ScreenGui’s contents in a single Frame and toggling its visibility.
- Yay
- Nay
0 voters
1 Like
I’d rather it be called Visible as Enabled is something different for certain gui objects
1 Like
But the ScreenGui instance itself can’t be seen, so “Visible” isn’t quite accurate.
BillboardGuis have an ‘Enabled’ property, so it makes sense to call it Enabled for screenguis
4 Likes
same with SurfaceGuis
1 Like
Should just move the Enabled property up from BillboardGui to LayerCollector (ancestor of ScreenGui, BillboardGui, and SurfaceGui) then
9 Likes
SurfaceGuis have Enabled. ScreenGui is the odd one out.
1 Like
I remember needing something like this once. Support.
Often your GUI happens to be all contained in a single frame, so ‘by coincidence’ you just need to check a single box to make it invisible and not need this feature. But not always.
Support
@baa_aaa
Why is it a mutator method instead of a property? SurfaceGuis and BillboardGuis both use an Enabled property instead of a method, so it’d be weird for ScreenGuis to (seemingly) randomly see the same feature as a method instead of a property. IMO the best change would be for Enabled to move up to LayerCollector (superclass of all three) instead of implementing the same thing in each three objects.
It’s not. @spotco was just going off the C++ convention. And yes, that is indeed how I implemented it. It will be out for release soon.
3 Likes