WeightLifts: Editing is fixed!

Fixed the issue with editing: update 2.1.0.4 is ready for download and contains the fix. Sorry for the trouble! 

Weightlifts: Editing is broken!!

Warning! I just found a glitch: editing an entry in a workout will cause your historical data to get overwritten! Avoid using the edit function until I fix it!

WeightLifts Coming Update 2.1.0.2

I just finished working on the next updates for WeightLifts and will release it after about a week of testing (so around April 7th to 9th). See how I went from 2.0.0.0 to 2.1.0.2? In my testing so far I've not seen any issues going from 2.0.0.0 to 2.1.0.2 (I finally sorted out the issue of it erasing all the data when making changes to the memory structure, so future updates shouldn't do that either)

Update 2.1.0.2 will have the following changes:

- The "goals" section has been replaced with a nice looking line chart instead. 
- Bug fix: Exercise Info now updates immediately after changes have been made. 
- The photo on the Exercise Info screen can be swiped to view a small line chart of the exercise history. 
- Added the ability to reorder exercises within a workout
- Added the ability to rename and reorder workouts in the workouts screen. 
- Added a bunch of new exercises to the default roster which will be installed automatically with this update. EXISTING DATA WILL NOT BE OVERWRITTEN. If you already have an exercise with the exact same name as one of the ones being added, you won't notice any change. 

WeightLifts Bug Fix: Statistics Search

I recently discovered a bug in the search feature of the statistics menu. When a user would search for an exercise, then tap the one they want, they would end up being taken to the statistics for a different exercise (the exercise they'd get taken to was actually the one at the same row number on the full list). I've got a fix ready, and it should be available in a few days. 

WeightLifts bugs - Pickers and secondary muscle exercises

I discovered 2 bugs in WeightLifts:

1) the Muscle group pickers weren't being filled out when a user edits an exercise by going: "Workout" -> "Exercise" -> "Edit"

and 

2) Secondary exercises weren't being populated. 

I've got these both fixed, and will the updated should be out shortly. 

WeightLifts Date Bug

I recently discovered a bug in WeightLifts that prevented entries made on single digit dates (so, November 7, November 8, etc.) from showing up properly in history and when exported. 

The cause of the bug was a change in the way dates were displayed after the update to Swift 3. 

I had set all dates to be formatted as "MMMM dd, yyyy" which meant that dates would show up as "November 07, 2016" for example. Note the "0" before the 7. After the update, however, Apple began removing the leading "0". Since I save all my date info as strings of text instead of date objects (I find it's easier to search for strings), when retrieving data (to populate previous workout info for example) the app was searching for "November 8, 2016" when the data was saved as "November 08, 2016" and thus not finding anything. 

I have corrected the bug, and will be releasing an update towards the end of the week (after some testing). This update will contain a little bit of code that will also go through and format all the date entries to the original double digit date style. For those of you with lots of entries, you may find slight delays when loading the app. I will remove this bit of code after 3 weeks, once everyone has updated. 

WeightLifts Update and iOS 10

It was brought to my attention that the workouts section of WeightLifts had a glitch where after adding an exercise, leaving, then returning, the exercise would not be listed under the workout. 

I have fixed the glitch and tweaked the code a bit so that the app doesn't hang while it loads all the exercise #'s and days since last workout. I also added a button to refresh the workout goals instead of it happening automatically each time that screen is pulled up. I noticed the system starts to get pretty slow once you hit 200 exercises, so this update should fix that. 

However, my Xcode did not update automatically, so I was not able to release the update on time. I've downloaded Xcode 8 but now I need to convert all the code from Swift 2.0 to Swift 3.0, a process that seems to be taking a lot longer than it should. 

As soon as everything's updated and working properly I'll have the update of the app out on the app store. Thanks for you patience!