Skutarth said:
I hadn't thought about it until now, but would it be better to not create the backups?
On one hand, the mapper files are tiny to begin with.
On the other hand, the backup files sure can get messy.
Maybe make it optional?
Another thing to consider with the addition of the virtual keyaboard a list of mappings is needed. Its mainly a selection of mappings from the default mapper. I dont know if those are in the mapper if this application would change some of them by mistake. I dont know how you can avoid it, maybe if the Vk mappings are present the user just has to not add them, or if they are change them manually.
Concerning the mappings, if any of the keys are above 255, the file is assumed to be up to date.
Thus, if you created it for the new version, it most likely won't modify it. And if you're converting the mappers from older versions (what this program is for), then the mapper files won't have any keys above 255 anyway.
That's if I'm not mistaken, of course.
You should try it out and see if there are any problems. Post again when you get the chance.
And it might be pretty hard to add an option for the backup files. As it is, I have it set up so it will easily catch any paths that have spaces in them (the space is obviously the delimiter for the arguments, and I'm pretty sure it can't be changed).
In other words, I could do it, but it sure would be a pain.
You might as well just do a search for "mapper.txt.bak" in Windows XP, for example, and select them all to delete them.
lets not worry about it, if someone has the VK mappings and they get messed up they can just copy paste from the example im going to provide with the release.
