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 icons size in group editor is not standardized #92361

Open
IkutiDev opened this issue May 25, 2024 · 9 comments
Open

Custom icons size in group editor is not standardized #92361

IkutiDev opened this issue May 25, 2024 · 9 comments

Comments

@IkutiDev
Copy link

IkutiDev commented May 25, 2024

Tested versions

  • Reproducible in v4.2.2.stable.official [15073af]

System information

Windows 11 Godot v4.2.2.stable.official [15073af]

Issue description

When assigning nodes inside group editor the sizes of custom icons are equal to the original picture size instead of being standardized to match other editor icons. Example screenshot:
obraz

Edit: Important to add I saw similar issues with other parts of editor which has been fixed since, so I'm guessing group editor just wasn't caught before, but it might not be too difficult to use the code that was used for inspector part of UI before.

Steps to reproduce

  1. Create a scene with some nodes that have custom editor icons that are normally bigger than standard editor icons
  2. Go to Node tab and select Groups category
  3. Press Manage groups
  4. Write a group name and press add
  5. See that both list nodes not in group and nodes in group show the original size of custom icons which can be large instead of being similar to standard editor icon sizes, making using group editor difficult

Minimal reproduction project (MRP)

N/A

@mews6
Copy link

mews6 commented May 27, 2024

could i try to check this out?

@mews6
Copy link

mews6 commented May 28, 2024

Little update: it seems to be replicable in a linux build of v4.2.2.stable.official https://github.com/godotengine/godot/commit/15073afe3856abd2aa1622492fe50026c7d63dc1 (building from Pop!_OS 22.04). I'm new to the project so i might have to dig around for a while to check what is causing it. Maybe it isn't resizing the icons properly or something, but it doesn't seem OS-dependant. If someone has different results, please let me know.

@IkutiDev
Copy link
Author

@mews6 I don't believe it's os oriented, my current guess is that it's related to this old issue #68962 where it was bugged for inspector and just that fixed wasn't added to group editor UI (guessing it's less used, most people assign groups via code and possibly don't use custom icons for nodes).

No one seems to be taking it right now so you are free to poke around. I would personally look into the PR that fixed the issue inside inspector. And than check if that fix can be applied to the file that creates the group editor UI.

@cselip
Copy link

cselip commented Jun 2, 2024

@IkutiDev would this just be groups_editor.cpp? (the file that creates the group editor UI)

@IkutiDev
Copy link
Author

IkutiDev commented Jun 3, 2024

@cselip Not 100% sure myself but I believe so, from a quick glance.

@mews6
Copy link

mews6 commented Jun 3, 2024

Currently taking a look at the file @cselip thinks might be the root of the problem, trying to check for anywhere where icons might be rezised, or if such a function even exists.

@Dowsley
Copy link
Contributor

Dowsley commented Jun 5, 2024

@mews6 this is the commit that adds resizing to the Editor 1522762

It seems to employ different strategies for each part of the editor.

@Dowsley
Copy link
Contributor

Dowsley commented Jun 5, 2024

#60965 removed the Group Editor and replaced it with an alternative that does not show which nodes that belong/don't belong in each group.

No node icon = problem solved. At least for now 😊

@elchukc
Copy link

elchukc commented Oct 9, 2024

#60965 removed the Group Editor and replaced it with an alternative that does not show which nodes that belong/don't belong in each group.

No node icon = problem solved. At least for now 😊

Do we close this issue then?

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

6 participants