[Kst] [Bug 128436] invalid fields should not be loaded as 0 (zeroes)

Nicolas Brisset nicolas.brisset at eurocopter.com
Fri Jun 2 09:27:37 CEST 2006

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From nicolas.brisset eurocopter com  2006-06-02 09:27 -------
Yes, that kind of makes sense. But it would be much better to check that the required field exists (using isValidField()) before initializing a (potentially large !) memory area and calling readField().
I don't think such cases are rare: many data files have "holes" and it could very well happen that a field which existed in the past is not in a newer data file. What surprises me the most, is that I remember seeing an error message of the kind "... file could not be loaded entirely due to missing fields" in such a case in the past. Has something been changed here, or is it just that there are other conditions to meet to get that message ?

More information about the Kst mailing list