Stats Part 3

 By Austin Evans 


    So this past week wasn't my best week. I was having a lot of trouble with the work I was given but what I worked on was the stats table. I was able to get the stats table to show the goals completed, by taking the goal history from our CUser class. This feature is used to show the user the number of goals they have completed since starting the app. The cool part about this is that if the user closes out the app, and goes back in the goals they have completed will still be there. 


This photo is a newer photo of the table but as of right now the user hasn't completed any of their goals. But if they do complete then the goal counter would count up in the stats table. 


With the older version of the table, I had the user track their total workout but it didn't make much sense to me on why and how to track the total workout. So I changed it to Routine Completed. Another thing I finished this week was to get the radar chart up and working with changing data. The original way I was trying to go about it was giving me a viewing error which was causing the app to crash when the stats page icon was clicked. I also got the button for the line to be view up and running.

With this button, the user will be able to see the line graph from anywhere in the app. The user would just tap the icon and will be taken to another page to view their progress in chart form.

      This past week was a problem one of the more important weeks for me since I had to do the stats table and get it working. Although not getting the radar chart up and running was the biggest impact on the project there since it pushed everything back. The efforts of this needed to be more and need to have the same effort going into the rest of the project.


    Approaching these problems was interesting. As I mentioned before, the radar chart was giving me an error about view the graph. To this day I am not really sure why I'm getting the error but I decided to go a different route to get the radar chart working. At first, I thought that I needed to try and get the data from the library into an ArrayList. But with stepping back from the problem and talking with my teammates I was able to figure a way to get it to work. By having the int called exercise counter and have it call the CUser class like I did for the goals completed in the stats table. After I would have to count the exercises for each muscle group. 

    For the button for the line graph, I also was having some trouble with that but soon figured out by brainstorming with my team that I was doing the code in the wrong class. I was working in our Exercise class and not our ExerciseData class which was causing the button not the work. So it was an easy fix by changing the class for where my code would go. After that, I really just need to add a case to the switch case saying that the button or icon goes to this activity. 

    Other than that, I have nothing else. I plan on working on the Line Graph and having the data go through the CDataEntry class so we can any type of data shown if needed. Thank you for reading and have a great week!


Comments

Popular posts from this blog

Time for Graphs and Stats

Up in Fire goes Firebase

Stats..... To be Continue