At the moment VoiceAttack uses UUIDs to identify individual commands, but creates these UUIDs at export time and does so each time an export is undertaken. This causes various problems on import of the commands in to an existing profile, for example the command executed on startup, if a phrase is unrecognised etc. need to be manually changed in the profile configuration each time a new import is undertaken.
There are a couple of options to fix this. The obvious one is to use the command's name rather than the command's UUID when importing (and from what I can tell it does this anyway when warning of commands being overwritten).
Another is to assign a UUID to the command at creation time and only update it if a genuine modification has been made. This has the added advantage of making profiles much more version control-friendly.
Either of these would make upgrading of third-party profile a lot easier.
Topic: Better handling of profile export/import (Read 4194 times)
VoiceAttack User Forums