UCommonButtonBase has a BlueprintCallable function `DisableButtonWithReason` that advertises that it should be used instead of `SetIsEnabled` because you can provide a reason. Since it takes an FText, it implies that this will be used to present a reason to the player and it even assigns the text to a member variable titled `DisabledTooltipText`. This text field is never used, however, and can’t be accessed by any means since it is a private variable. There’s also a completely unused `EnabledTooltipText` property.
I think that these two text fields should be used to set the tooltip of the button automatically as it is enabled or disabled. There should also be a way to set `EnabledTooltipText` so that it can be used for this purpose.
Steps to Reproduce
Have a project with the CommonUI plugin enabled.
Create a widget and derive from CommonButtonBase.
Use that widget in another widget to place it in the viewport.
Disable the button with the function `DisableButtonWithReason` and provide a reason.
[Bug] Button is disabled, but the reason is not surfaced to the player.
Hi,
Agreed, this looks to be a bit of functionality that was never completed. I’m guessing the intent was to cache the tooltip text set in the editor (a property of SWidget) and swap it out with the disable text when appropriate. I’ll make a note to see if we can clean this up, I’m not sure it makes too much sense to finish the implementation since it leaves some open questions around behavior (i.e. if a widget has no enabled tooltip, should it display the disabled text in a tooltip or not?)
Best,
Cody