The downfall of import a csv file
By Austin Evans
This past week hasn't been the best week. I was tasked to get the imported file to show up on the routines page but to no luck. Since we are two weeks away from having the app finished, we had to think up another solution. So my teammate came up with saving the file as a binary file and not a CSV file. Since we are not saving the total amount of data to the CSV file, having it load in causes problems. Like not having the exercises show up.
Another thing that was a bust was to import a file from another app. Going with the app called WorkIt that my teammate suggested the file is saved additional information like date, cardio, and some other information. But since we have the additional data pulling in the file causes a NULL error toast. But to get around this problem we decided to scrap the idea for now and return to the issue at a later date.
However, not everything that was done this past week was a bust. I was able to get a bug where the app would crash whenever an empty file would be export. However, getting this bug fixed was really easy. I created a new activity for the export and an activity class for the export also. By moving the code other there and having a startactivity() function I was able to get the bug fixed. I am thinking that the app was killing the app before returning to the app.
Other than that I really didn't have much to work on since I am working on my second class also. This upcoming week is going to be a semi-easy week since I am looking for a library on pop windows since we want to have an X at the top of the window. I am also working on getting the slides for post modem up and running.
Comments
Post a Comment