This has no real effect on the behaviour of the deployed VANTED application, since it occurs on while developing for it. Essentially, if you use some Preferences for a class and then modify this class by means of renaming, moving or deleting altogether, you still end up with its Preferences being stored in the VANTED settings.xml file.

A way of fixing it, is simultaneous removal of the preferences in question from both the Java User Preferences (under Linux ~/USER/.java/.userPrefs/) and the settings file. Only deleting from the one of the two, rewrites them in the other.

This has no real effect on VANTED behaviour, since it occurs on while developing for it. Essentially, if you use some Preferences for a class and then modify this class by means of renaming, moving or deleting altogether, you still end up with its Preferences being stored in the VANTED settings.xml file.

A way of fixing it, is simultaneous removal of the preferences in question from both the Java User Preferences (under Linux ~/USER/.java/.userPrefs/) and the settings file. Only deleting from the one of the two, rewrites them in the other.