Descriptive Problem Summary:
Setting is-disabled on a label at runtime forces the label to become visible, despite the is-visible parameter being true or false.
Numbered Steps to Reproduce Problem:
Download my demo. If you pop open the interface, you'll notice two sets of labels and some other irrelevant controls. The right four labels are set at compile-time to match their description, while the left four are set in mob/Login() at runtime with winset(). Notice that the behavior differs in that in the dynamically-set labels, the disabled and invisible one is visible despite is-visible=false clearly being set, and outputting winget() after making that output default verifies.
Expected Results: The two bottom labels in both sets would be invisible, with the very bottom one being disabled.
Actual Results: The bottom left disabled label is actually visible, despite having is-visible=false.
Does the problem occur:
Every time? Or how often? Every time.
In other games? Yeah, Chatters.
In other user accounts? Probably.
On other computers? Super Saiyan X verified.
When does the problem NOT occur? When you don't set is-disabled at runtime.
Workarounds: Don't set is-disabled at runtime, I suppose.