I'm attempting to write a GUIeditor for F1C PLR files. It's coming along
nicely.
I've got the basics there now, and I've just got to the point of looking at
which lines of the PLR file to parse.
There are a lot of lines in this file, and I'm sure that they're not all
needed in a GUI, so can anyone give me a list of the ones that are worth
bothering with?
Thanks.
--
R.
GPLRank +79.699
> I'm attempting to write a GUIeditor for F1C PLR files. It's coming along
> nicely.
> I've got the basics there now, and I've just got to the point of looking at
> which lines of the PLR file to parse.
> There are a lot of lines in this file, and I'm sure that they're not all
> needed in a GUI, so can anyone give me a list of the ones that are worth
> bothering with?
> Thanks.
why don't you just parse them all, make the most important
variables "clickable" in some manner and leave the others that
you don't bother with on a separate tab, as text fields that
"advanced" users can change?
Also, what language are you using? If you use Python it should
be a breeze creating a dictionary (called "hash" in other
languages like Perl) on the fly that can be changed and written
out again programmatically.
All the best & good luck,
uwe
--
mail replies to Uwe at schuerkamp dot de ( yahoo address is spambox)
Uwe Schuerkamp //////////////////////////// http://www.schuerkamp.de/
Herford, Germany \\\\\\\\\\\\\\\\\\\\\\\\\\ (52.0N/8.5E)
GPG Fingerprint: 2E 13 20 22 9A 3F 63 7F 67 6F E9 B1 A8 36 A4 61
