Unfortunately I tried cheating by not doing a skin reset or saving and replacing the skin settings.xml but I finally just gave in, it was the only way I could get things straight. I even tried comparing the settings.xml created after the reset with the existing one but there are too many differences given my extreme level of customization. So yeah, I spent a couple days just getting my main menu and submenus mostly back close to how I like them, for the second time in as many months. Now I'm wondering if I'm wasting my time because @
latts9923 makes it sound like every time he adds a view it will require a reset? This is not a deal breaker and in no way detracts from the excellent work he is doing porting his mod to MQ9, so once again, thank you @
latts9923.
The only idea I have is that the next time a reset is required is to save the ...\
userdata\
addon_data\
skin.aeonmq9\settings.xml with your customization. Then reset the skin before applying the update and saving that settings.xml (which will be pretty much default) settings.xml as well. Apply the update and reset again. Then compare the pre and newly created post update default settings.xml files isolating the new lines and add them to the settings.xml with the customization and then using that one. Now, having said that I don't have enough experience with a file comparison program to confidently do this myself so perhaps someone with better knowledge of and more experience using a file comparison program like WinMerge could give this a try and share their results? If a user steps forward I'll be happy to explain my idea better or provide the files to compare?
Until then if anybody comes up a workaround for this issue please let us know? If not it looks like we will all be doing our settings at least (say it with me in your best Mexican accent) One More-time.
Cheers, Juan Mortyme