As stated, there is currently no option in the configuration to use previous values for display names, short display names, cars, teams, and points when creating or editing a configuration file. You can either hit ENTER a bunch of times, or enter -1 to use the same value for everyone, but no option, like in the points structure, to use the previous values.
There are some technical challenges to this. Because of the garbage that accumulates in the UDP packet data, "SenorPez" might be best-guessed as "SenorPezaud8547" in another race, or "SenorPezantos" in another. We get around this by prompting for a display name in case the best-guess algorithm can't get through all the trash. Since we use the best-guessed name as our dictionary key (since using the user-provided display name would be messy at best and dangerous at worst), the program won't inherently know that "SenorPez" in Race 1, "SenorPezaud8547" in Race 2, and "SenorPezantos" in Race 3 are all the same person. (Nor could we assume that, as you might have a race with a bunch of people in the same clan, thus, same name prefix.)
Probably the best way to implement this would be this:
Prompt for Display Name. This means you, unfortunately, can't do a "Use Previous Values" for Display Name. Tough.
If the Display Name matches a previously-used Display Name, we start the routine to offer the option of matching that previous data with the current data.
Error states?
If you mistype your Display Name, there's no match. You should have typed better.
If you have non-unique Display Names, you get what you deserve. Why would you have non-unique display names?
As stated, there is currently no option in the configuration to use previous values for display names, short display names, cars, teams, and points when creating or editing a configuration file. You can either hit ENTER a bunch of times, or enter -1 to use the same value for everyone, but no option, like in the points structure, to use the previous values.
There are some technical challenges to this. Because of the garbage that accumulates in the UDP packet data, "SenorPez" might be best-guessed as "SenorPezaud8547" in another race, or "SenorPezantos" in another. We get around this by prompting for a display name in case the best-guess algorithm can't get through all the trash. Since we use the best-guessed name as our dictionary key (since using the user-provided display name would be messy at best and dangerous at worst), the program won't inherently know that "SenorPez" in Race 1, "SenorPezaud8547" in Race 2, and "SenorPezantos" in Race 3 are all the same person. (Nor could we assume that, as you might have a race with a bunch of people in the same clan, thus, same name prefix.)
Probably the best way to implement this would be this:
Error states?