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

Remember region settings in AtlasTexture region editing dialog #9366

Open
perroboc opened this issue Mar 23, 2024 · 0 comments
Open

Remember region settings in AtlasTexture region editing dialog #9366

perroboc opened this issue Mar 23, 2024 · 0 comments

Comments

@perroboc
Copy link

perroboc commented Mar 23, 2024

Describe the project you are working on

Game with a couple of spreadsheets full of different icons. Both spreadsheets have different settings (the first one has 100x100px icons, while the second one 128x128px)

Describe the problem or limitation you are having in your project

I've created 2 spreadsheets with different settings (100x100, 128x128), and use them to create different icons in the game by creating AtlasTexture resources and editing the regions.

The problem is moving when clicking "Edit Region" in the TextureAtlas button, the Region Editor does not use the Texture Atlas properties as initial values, it uses the ones from its last session, so this happens:

image

and every time I switch between the spreadsheets, I have to set the initial values again.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Remembering the values per TextureAtlas would be a great help to save time and not having to set the values every time I switch between spreadsheet with different sizes.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

The TextureAtlas hopefully has this information in its resource, which could be used by the editor.

If this enhancement will not be used often, can it be worked around with a few lines of script?

Not sure

Is there a reason why this should be core and not an add-on in the asset library?

Because it already is a core feature, and could be enhanced.

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

3 participants