Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom tooltip showing when no tooltip text is set #99675

Closed
filkata opened this issue Nov 25, 2024 · 5 comments · Fixed by #99679
Closed

Custom tooltip showing when no tooltip text is set #99675

filkata opened this issue Nov 25, 2024 · 5 comments · Fixed by #99679

Comments

@filkata
Copy link

filkata commented Nov 25, 2024

Tested versions

Reproducible in 4.4-dev5, 4.4-dev4
Not reproducible in 4.4-dev3, 4.3 stable

System information

Godot v4.4.dev3 - Windows 10.0.19045 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 32.0.15.6094) - AMD Ryzen 5 1500X Quad-Core Processor (8 threads)

Issue description

Previously if a node had a custom tooltip setup using _make_custom_tooltip() but has no tooltip text set -> no tooltip would be shown. In 4.4-dev4 and 4.4-dev5 an empty tooltip is shown.

Steps to reproduce

Hover over the TextureButton in the MRP.

Minimal reproduction project (MRP)

tooltip_bug.zip

@timothyqiu
Copy link
Member

This is an intended change, see #97961.

Now _make_custom_tooltip() takes full control of the tooltip logic and is called regardless of whether get_tooltip() returns an empty string.

To obtain the old behavior, check the argument at the beginning of _make_custom_tooltip() and return null if it's an empty string.

@Mickeon
Copy link
Contributor

Mickeon commented Nov 25, 2024

While this is intentional, should not be denoted as a somewhat breaking change?

@filkata
Copy link
Author

filkata commented Nov 25, 2024

I wonder if this warrants a mention in the documentation?

@timothyqiu
Copy link
Member

While this is intentional, should not be denoted as a somewhat breaking change?

Indeed. How should this be denoted?

@Mickeon
Copy link
Contributor

Mickeon commented Nov 25, 2024

First of all, I think we should tag the original PR as breaking compatibility(???). So that, when it's time, a page like Upgrading from Godot 4.2 to 4.3 can include this change, as well, without having to manually remember everything.

@AThousandShips AThousandShips added this to the 4.4 milestone Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants