possibly attach a listener to the container to alert whatever model it's a part of to update if the underlying core data entity changes
this will also prevent threading issues accessing core data entities for processing off the main queue

One had a variation and they didn’t save the variation fly 10 and fly 10 barefoot

_{Sent with GitHawk}

repeated crashes on loading models for progress charts off main thread.. particularly accessing dates

they both need search functionality, and a segmented control to toggle between sorting by category and alphabetically -

want to re-use a lot of infrastructure, in fact, almost all of it. But thinking about creating a separate database table for flexibility exercises? or just a flag field in exercises?

Want to give users very well defined boundaries between exercises and flexibility/mobility movements so as to do things like provide a dashboard of PRs versus mobility PRs.

If they were separate database tables, could join them in the app through protocol inheritance to do common things to converting to proper units and finding records, so on.

You can have a switch in the "create exercise" that marks an exercise as mobility/flexibility - same thing w/ categories - you could have a switch on the category, a flag that designates that all exercises in it's bucket are mobility/flexibility - search for them w/ table join

you probably don't want to use an estimated 1RM as the progress marker.. maybe just put best sets side by side

beside "Done" button

showing the time in the Length and Time fields eg "1:40 x 2 x 1:40"

or the user presses 'finish workout'
need to be able to handle that intermediate state

embed a video of the app in use at the bottom

on this line:

var primaryMetric: Metric_Info {
        return self.max(by:{
            $0.metric.primaryMetricOrder > $1.metric.primaryMetricOrder
        })!
    }

Need to use a struct when doing personal records instead of a core data entity

right now it's too wide

so that the viewer knows where they just pressed
in current wrkout

autolayout issue I think

add border rows on main workout page
give "add exercise" btn a solid background

they are incrementing by one instead of reflecting the real week number

set it so that you can't have duplicated metric infos, and that when you update/change them, they get fixed in update Exercise

align things on the left or right side of screen, I don't like middle aligned items

when entering sprint exercises.. seconds are rounded up/down

_{Sent with GitHawk}

entering minutes and seconds, i.e. 2 in min field and 30 in sec field, doesn't show up correctly. Only shows as 2 min and 0 for seconds.

make sure that week labels reflect actual week and aren't only incrementing

crashed at

 var sortedByDefaultOrder: [Metric_Info] {
        return self.sorted(by: { $0.metric.defaultOrder < $1.metric.defaultOrder } )
    }

make sure all buttons highlight when pressed

if you check a complex in 'Search Exercises', it won't be added to your exercises/ categories

when you click on a header metric to sort, allow it to sort in the opposite direction if you click it again. Consider putting an arrow or something there to indicate which direction it's being sorted in

Assemble the exercises vertically or consider a text box that expands

Don’t allow dismissing the exercise picker and give some options about selecting exercises from all the exercises and not just ones that are active

_{Sent with GitHawk}

the navbar isn't laid out until the last minute and it flickers, same w/ the title "Workout History" -
if you need to reload a row in workout history because the date changed, send the row data/function
before the segue. set up a delegate with the tableView delegate ie whoever handle didSelectRow(at:)

textbox in uialertview (done in Resources1.0)
check to make sure a category w/ same name doesn't already exist

only has weight/sets/reps right now

is was blue after deleting a workout, red after selecting it, and black by default

See list

_{Sent with GitHawk}

to see in kg or lbs

So that you can then convert them up to min or feet, if needs be, when you display them.. but otherwise don't keep ft or min as the "display" unit and convert them s as the save unit, to ft as the display unit, and then to min:s as the display format

_{Sent with GitHawk}