Sweet. Thank you!
Couple of related questions:
when I’m using your config editor and I can save various configs at the top of the page, where are those being saved? Are they just in the cookies of my browser? Is there any way to import an existing config and have the editor parse it so I can make changes?
Thank you again for all this. I love tweaking stuff and all your various tools make it so much easier.
They are saved in Local Storage on your browser.
I don’t have a way for my tools to parse configs, they merely assemble things based on the options you select. The are made to put things together, I don’t have the tools to be able to break things apart, it’d be considerably more complex to be able to handle external files and parse them into the options.
I am trying to use style options and using functions to get optimized versions of all the greyscales styles. When using your rebuilt versions of Greyscale styles and adding the greyscales style option “Defect” to any group of other greyscales styles or when I add it by itself, the “power” button used to retract the saber on the preview/enhancements screen does not work. This means that preons, ignitions, ignition powerups, retractions, retraction cool downs, and post offs cannot be previewed if “Defect” is included as a style option. This happens without selecting any enhancements. I’m not sure if this bug is limited to the preview/enhancements screen or if it would cause a problem when added to the board. I do know that if I go ahead and get the style code and paste it as a using function, the problem does propogate to the “preview style” button on the config helper page when trying to build presets using that using function.
Thanks, I’ll try to take a look this weekend.
I have fixed the “defect” in Defect, you’ll just need to refresh the library to get the updated script.
You rock! Thanks so much for all that you do, man. BTW, i see that you added some of more of these optimized versions of greyscales fonts (extra crispity ones too) since you did your video on how to use option styles and using functions, do you plan to do all of them?
Eventually, it’s been harder to find time lately, but it’s on the to do list.
Are there preferred groups of greyscales options to include together to save memory? Or rather, what is the best way to group them to save memory? I am omitting preons and postoffs because I find them irritating (hope that will save some memory too).
There isn’t any specific. The bulk of the saving is the shared effects and the common syntax and obviously using a single style in multiple presets.
If you have presrts that you wanted similar effects other than the base style, grouping those would be better but if everything besides the base style is the same the groups won’t make too much difference in my experience.