ClipsDescendants

[Imaginze]

(I saw that this have been posted a lot and still to be fixed…So i wanted to post it too as a reminder.)
When you rotate a gui object with any deegrees, the ClipsDescendants property stops working.

Hope it gets fixed because it is a very serious problem for some (example me).

[YasuYoshida (Yasu)]

This isn’t a bug.

[Imaginze]

Then there must to be a way of this not happening, is there?

[Partixel]

Use an image instead of a rotated gui

[Elmuowo (Elmu)]

Yeah this ain’t a bug it’s intended behaviour.

@stravant

The reason that this wasn’t handled at the time is the case of rotated objects inside of rotated objects.

Clipping rotated objects inside of unrotated objects isn’t particularly hard (But still non-trivial), but once you introduce a rotated clipping region it becomes a lot more tricky to implement things efficiently, and it would have significant performance implications that would not be immediately obvious to the developer using it.

I’m sure that the feature will come eventually in some form for the sake of completeness, but it’s definitely one of those “eventually” features that I don’t expect to see it the near future.

More information here

Make GUI Rotation effected by ClipsDescendants

Clipping isn’t as easy as you’re making it out to be: A GUI can be visible in a clipping parent even if none of it’s vertices are inside of that parent, and it can also be visible even if none of the parent’s vertices are inside of it. And, the hard part is that for an arbitrarily rotated hierarchy of GUIs, you may end up with an effectively arbitrary convex polygon clipping region for a given GUI. In one approach you would end up doing a bunch of operations of clipping an arbitrary polygon wit…

EDIT:
I found all this by simply searching “ClipsDescendants” in the forum search, and that thread was the first one that came up.
You might want to search before posting new threads

[Imaginze]

I like posting

[sparker22]

Search first.

[buildthomas]

Asking about it in developer discussion is okay-ish if it’s a duplicate (although preferably not), but when you post in bugs / feature requests you should make sure that it’s not a duplicate always.