[Kst] [Bug 120827] Command line option -f fails for some asciifiles
tskisner.public at gmail.com
Mon Jan 30 04:17:13 CET 2006
On Sunday 29 January 2006 17:55, George Staikos wrote:
| API changes are not necessarily a problem. We're using a plugin-key now
| so it shouldn't be too much of a problem. The only issue is that it forces
| people to change their plugins when they update Kst, but at least they
| don't crash Kst randomly.
I thought we were frozen for 1.2? Or do you mean API changes for after 1.2?
| > Perhaps as a stop-gap measure, we could have the datasource scan the
| > first 50 lines (or some large-but-not-performance-killing number) of the
| > file and take the maximum number of fields as the number for the whole
| > file. How does this sound?
| That sounds better to me, but again, API changes are not disallowed at
| this point.
Ok, I think this is the easiest to implement given our need to get 1.2 out
immediately. I'll come up with a patch ASAP and post for review.
More information about the Kst