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

Packager should be able to read the config json comment in the stage sprite #759

Closed
ffghdfh opened this issue Aug 30, 2023 · 6 comments
Closed

Comments

@ffghdfh
Copy link

ffghdfh commented Aug 30, 2023

Honestly this is only a small inconvenience, but every time I hit package project and the packager hasn't been open for a while, I have to manually enter the fps, the stage size and so on and so forth, and I think it'd be really cool if it could automatically read the info from that json file that is saved as a comment to the stage, and set the settings accordingly.

@TheShovel
Copy link

The packager removes all comments. They don't exist in the final file.
If you want, you can use the Runtime options extension and set all the values when the project starts.

@ffghdfh
Copy link
Author

ffghdfh commented Aug 30, 2023

But i'm not talking about the final file, i'm talking about how when you load in a .sb3 file, it should read that comment to fill out the runtime options part of the packager, aka this stuff
image

@ffghdfh
Copy link
Author

ffghdfh commented Aug 30, 2023

that's peculiar, i just noticed that it said "this project has settings stored in it, which may override these settings." but then how come that when i usually load in a file, everything there is in it's default state?

@TheShovel
Copy link

Ooh alright. The settings in the project file itself should actually change the values displayed in the packager instead of just saying that there are overrides. Not having it do that can be a little misleading.

@ffghdfh
Copy link
Author

ffghdfh commented Sep 2, 2023

Ooh alright. The settings in the project file itself should actually change the values displayed in the packager instead of just saying that there are overrides. Not having it do that can be a little misleading.

Yep, (sorry for the late reply but) I completely agree! Or in the very least, disable any form of input for those fields.

@GarboMuffin
Copy link
Member

im going to close as a duplicate of #213

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

No branches or pull requests

3 participants