April-11-17 debug/bug

With the current version(Apr-11-17), Nvil is creating a "restoration copy" of the config files. Is that now a default or left over from debug version?.
Also, I use the "snapping sprites"(nvil/media/AnimationDesign/Snapping Sprites/(gif files) in my user buttons, but they no longer loaded from my config, I am having to re-link them.

With the current version(Apr-11-17), Nvil is creating a "restoration copy" of the config files. Is that now a default or left over from debug version?.

It is a default now. Just in case when the config files get corrupted or damaged, there is a copy for restoration if user didn't back up his config files.

Also, I use the "snapping sprites"(nvil/media/AnimationDesign/Snapping Sprites/(gif files) in my user buttons, but they no longer loaded from my config, I am having to re-link them.

Once the image is assigned to user button, it stays in the config files. Can you send me your old confige files so I can have a look why it didn't load. Also did you have any other buttons that have images and did the images get loaded?

It is a default now. Just in case when the config files get corrupted or damaged, there is a copy for restoration if user didn't back up his config files.

Not sure as to how that will help considering the "restoration copy" is a copy of current config that may be corrupted.

Once the image is assigned to user button, it stays in the config files. Can you send me your old confige files so I can have a look why it didn't load. Also did you have any other buttons that have images and did the images get loaded?

I have made quick test with new config.
I added one user window/button with image in build Mar-6-17. Using that config in build Apr-11-17, the button image does not show. So it is not a problem with my config, but with whatever changes you have made to Nvil.

Looking in the "UserButtonToolSettings.xml" where the image data is stored, it has been removed by Apr-11-17 build.

When loading settings, if any error occurred, a message will appear to indicate the setting files may be corrupted and a restoration is needed.


In the new implementation, button images are moved to a different file. There is a mechanism used to migrate those images. That mechanism didn't work properly. It is fixed in the new update, Apr 14 2017.