Thanks for taking the time to check it out. Since I don't have any testers I have to rely on those using the program to give me the info on a crash.
It has happened to me as well when the list files get messed up, somehow. Nothing from what you have done. If there are no changes to the data then all it should do is write out the same information, so that isn't the problem
The reason you are getting the error message is because there are two lines within the file with the same key. The key is derived from the command name. If there is an equal sign it uses that as well. If not then it is just the command name. What program does is re-write the def file with the new changes (or not) and add it to a "collection" with a key. Again, if there is a duplicate then it will crash. Need to at least prevent that from happening
So, it is possible you are trying to add a command that is the same as the one that is already there. If I remember correctly there is at least one of your command variable names that is the same as "varcommand
=X." I'm not sure which one or more it would be. Even though you also have a variable of Y for the command "=X Y", it doesn't pay any attention to the "Y," as I mentioned before. The only thing you could do in this case is delete the FPSC variable command so you can add your mod variable.
At least I need to catch this error and use an error message rather than having it crash and burn.
Since I know your commands I will try this at home.
The list and def files that are installed has all the FPSC variables through version -- gosh I can't remember, maybe through 1.12? I guess one would have to look at the lists provided on the right hand side of the window when a fpi document is active.
I will definitely give this some serious attention now and come up with a "fix." It really isn't a bug but needs to be dealt with. Well, it depends on one's definition of "bug".
No, it is a bug, programmers don't like to think that they cause bugs.
Ply, could you send me the commands lists and defs? Would be very helpful. They are located in the root directory of the application.
The past has a lot of memories to hold onto; but, today is chock full of new adventures, and, the future shouts out, "The best is yet to come!" -- TerryC