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

When typing a hex color into a resource, the popup prevents keyboard input #80018

Closed
MichaelMacha opened this issue Jul 29, 2023 · 3 comments
Closed

Comments

@MichaelMacha
Copy link
Contributor

Godot version

4.0.3

System information

Linux Mint 21.3

Issue description

I'm working on a game with items as their own resource class, each of which has a UI color associated with it. While moving from a previous, more haphazard, method of simply including all names, scenes, colors, and so on in parallel arrays; to a more compact version that simply keeps a single array of a custom resource with all necessary properties, I must copy a color from one array to another.

This wouldn't be that big a deal, as I can just copy the hex code for the color; but the moment that the descriptive popup shows up ("Enter a hex code '(#ff0000)' or a named color ('red')") I can no longer enter text with my keyboard until I click off of it. Seems like a UI rules conflict.

Unfortunately, my screen capture key seems to hide the popup, or I would share an example.

Steps to reproduce

Create any class, extending Resource, with a color as a component. Add the resource to an array in another class, and click on the color, then attempt to type in a hexadecimal code. Note that the popup prevents further input until you remove it.

Minimal reproduction project

Probably N/A, this should happen for just about any product.

@AThousandShips
Copy link
Member

Can you replicate this on 4.1.1, or 4.2.dev?

@tokengamedev
Copy link

Issue of tooltip grabbing focus has been raised multiple times. These issues are collated and fixed under #73926

@Sauermann
Copy link
Contributor

That seems right. Closing this as a duplicate of #73926.

@Sauermann Sauermann closed this as not planned Won't fix, can't repro, duplicate, stale Jul 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants