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

Proposal - Allow specifying name and export location of the generated atlas file #22

Open
VisenDev opened this issue Oct 2, 2023 · 4 comments
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone

Comments

@VisenDev
Copy link
Contributor

VisenDev commented Oct 2, 2023

It would be nice to have some functionality which would allow you to specify where the atlas file is sent to, and what it is called

@foxnne
Copy link
Owner

foxnne commented Oct 3, 2023

I think this may just be an issue of how I set it up, but when you click Export on the Pack window, it should open a native file dialog to select where you want the atlas to be saved. The name you input here will be the name of the exported atlas and image. It's just not clear that all you need to input is a name with no extension as .png will be added to the name for the image and .atlas for the atlas.

@foxnne foxnne added enhancement New feature or request good first issue Good for newcomers labels Oct 3, 2023
@VisenDev
Copy link
Contributor Author

VisenDev commented Oct 3, 2023

the name you input here will be the name of the exported atlas and image

Yes, I know you can specify where the output folder is, what I meant is using a different folder for the exported png and for the exported JSON data

For example, putting the png in the images folder of your game, and the .atlas in config

and what it is called

By this I meant that you could specify a custom name for the exported atlas, such as textures.json instead of using .atlas

Hope that clarifies

@foxnne
Copy link
Owner

foxnne commented Oct 3, 2023

Ah okay! Yes that does. I'll have to think about the best way to go about it, but I think that's doable.

@foxnne foxnne added this to the 0.2 milestone Oct 3, 2023
@foxnne
Copy link
Owner

foxnne commented Aug 2, 2024

I think @slimsag had a better suggestion for this: we need a config file for a "project". It shouldn't be required for pixi to allow editing files and exporting simple things, but maybe it should be required to use the packing functionality. If a .pixiproject file is located in the root folder, it will be read for project specific settings, such as export file names and paths, ldtk compatibility, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants