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

pset naming issues #1086

Closed
tehn opened this issue Apr 13, 2020 · 4 comments
Closed

pset naming issues #1086

tehn opened this issue Apr 13, 2020 · 4 comments
Assignees

Comments

@tehn
Copy link
Member

@tehn tehn commented Apr 13, 2020

  • When you save to slot 1 you can only name the PSET with the name of the script. For eg. with Moln, whatever I write into the field the preset will always just be called “moln”.
  • locations other than 1 seem to work at first. But when you try to overwrite the preset, you’ll get presented with the default name again.
@tehn tehn self-assigned this Apr 13, 2020
@papernoise
Copy link

@papernoise papernoise commented Apr 13, 2020

So far it seems to me that this happens only with some scripts. Molly the Poly for eg. seems to work fine. I can test through more scripts to see if there's a pattern.

@papernoise
Copy link

@papernoise papernoise commented Apr 13, 2020

ok I went through a couple of scripts.

I tried thiese: Awake, Molly the Poly, Bounds, Cheat Codes, Circles, Moln
giving presets a custom name works the first time, but when overwriting them I get the default name again.

Last time I tried things were a bit more random. For eg. Moln wouldn't let me enter a custom preset name at all (on any slot), and Molly the Poly was working as expected.

Tried Otis then, and it would have the same issue as I previously had with Moln. It would not let me enter a custom preset name on the first slot, always just showing "moln".
The name would still revert to the standard "otis" when overwriting an existing preset.

For now this seems to be happen a bit randomly, I need to investigate this further when I have a moment.

@tehn
Copy link
Member Author

@tehn tehn commented Apr 13, 2020

thanks for the feedback.

let me have a go at a fix before you dive back in.

@papernoise
Copy link

@papernoise papernoise commented Apr 13, 2020

Sure, no problem!

@tehn tehn mentioned this issue Apr 21, 2020
@tehn tehn closed this in #1099 Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants