Ulf Dittmer wrote:So now everything works ?
Ulf Dittmer wrote:What is the point of storing data as file (no matter the format) if the same app reads it later? Why not keep it in memory?
Ulf Dittmer wrote:You misunderstood. What are the *actual* values? Not what you think they are, but what they actually are. Print them out and make sure they match your assumptions.
Ulf Dittmer wrote:In that case, an answer to this would be helpful:
Ulf Dittmer wrote:What are the values of the elements of the "a" array for the line that's giving you trouble?
Ulf Dittmer wrote:
the problem is that no matter what I try, I cant access the 4th element and use it to draw an extra line to the chart.
normalList.add(Integer.parseInt(a[3]));
The code you posted seems to do just that, so what exactly happens when you you run? TellTheDetails
Ulf Dittmer wrote:What do you mean by "call out"? What exactly is the problem? The code shows how to access the 3rd element - what prevents you from similarly accessing the other elements?
Ulf Dittmer wrote:
but if there is 5 practices per week for a 6 month period, wouldn't it be better to have it stored in file somewhere?
We don't know what that data is intended for, that's why I asked. My question was not about long-term storage, it is about the fact that the app writes to a file and then reads form the same file - that seems inefficient to me. Why convert Java objects to a file representation only to convert that back to Java objects within the same app? (Especially if it gives you problems, I might add :-)
At a quick glance, the CSV looks OK. What are the values of the elements of the "a" array for the line that's giving you trouble?
Ulf Dittmer wrote:Have you looked at the CSV to see if it's properly formatted? Post it here.
What is the point of storing data as file (no matter the format) if the same app reads it later? Why not keep it in memory?
Aug-30-2014,08:06 AM,0,0,0
Sep-05-2014,08:09 AM,0,3,2
Sep-05-2014,08:10 AM,0,3,2