GS Beta 7: Pre-Existing Macros Breaking on Save/Update to Caps

Question

GS Beta 7: Pre-Existing Macros Breaking on Save/Update to Caps

Opened this issue 6 years ago · 2 comments

Deleted user commented 6 years ago

Just a small issue that i guess has existed since Beta 3.

If you have an existing macro pre-upgrade (i am using this in live too) it will be in lower case. Not a problem, it still works.
When you update/save your macro it will then save this macro as caps on the viewer and storage only.

Icon on the action bar will still be lower case.
Can no longer delete the updated icon on the viewer because the macro in /m is still lower case and can't be orphaned by GS.

Fix to make this work is to delete the existing macro in /m which turns the macro back into a book and then re-create the icon and drag it. Macro icon at that time will be created in caps

This only affects existing macros. New and Imported are perfectly fine as the macro in /m is not created yet.

TimothyLuke · Answer 1 · 2018-05-02T21:16:09.000Z

I’ve thought of this. There is a one off action that runs when you first install 2.3.00. It will update all the macros to upper case and remove the original version. It then runs a cleanorphans. This only ever runs once so for people upgrading from 2.2.08 to 2.3.00 this process will prevent this problem. It was introduced with Beta3 but it’s only with 4+ that we have all processes working with upper Cade properly. If you look at the GSE.lua file there will be a setting that is upgrade801 = true (exact spelling within vary as I’m doing this from memory). Setting that to False and logging back in will do this en masse. /run GSEOptions.upgrade801 = false Then log out and back in. (Please check that the upgrade801 is the exact spelling of the setting. It’s also into the RunOnce.lua file) TimothyLuke

…

On 3 May 2018, at 6:22 am, Cymiryc ***@***.***> wrote: Just a small issue that i guess has existed since Beta 3. If you have an existing macro pre-upgrade (i am using this in live too) it will be in lower case. Not a problem, it still works. When you update/save your macro it will then save this macro as caps on the viewer and storage only. Icon on the action bar will still be lower case. Can no longer delete the updated icon on the viewer because the macro in /m is still lower case and can't be orphaned by GS. Fix to make this work is to delete the existing macro in /m which turns the macro back into a book and then re-create the icon and drag it. Macro icon at that time will be created in caps This only affects existing macros. New and Imported are perfectly fine as the macro in /m is not created yet. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Deleted user · Answer 2 · 2018-05-02T21:48:51.000Z

Found it as Upgrade801 = true

It did seem to work, it ended up orphaning my existing lower cases and left me to go ahead and create new icon 👍

Share to