75 votesOxana Tkachenko commented
Also, you could add a graphical-user-interface for user to specify header-containing lines of the file. It would make analyzing the contents of the file faster, especially when user has many files of identical size (many simulation results for the same mesh).Oxana Tkachenko commented
It would be nice to have better messages, warnings and errors in Paraview, so that the user would be able to understand why the file couldn't be read.
If you don't understand a token in the header, just skip it, don't crash because of it. For example: "C=Green" is purely aesthetic and can be skipped. User may frown, but it will work. "StrandID=7" and "SolutionTime=1.2" are more serious, since it may be needed for time animation, but skipping it will work, too.
Also, I don't understand yet how it reads the variables. Not even X, Y, Z. There are some variables, yes, but their values are not what I expected to see. And when it shows the slice of "T", the points are shown like a parabola. Something is wrong. Do you expect commas between tokens? Are you prepared to extra spaces around "="? Do you require quotes around variable names? Does CapsLock confuse you? Should I add "Title=..." header to the file?