#703 Captures dated by FM
Ross: "Change Captures away from jan, feb, mar etc use date in FM when capturing", "I don't want to limit what a user can catch, if they want to catch details every day in july then so be it", and "when you add a team you specify its league start and end months". The probe found the date in FM's navigation bar (CurrentDayWidget: Month "2/9/2025", WeekDay "Tue", Time "00:00"), readable on every screen. Everything below is computed from the controls: the season rule, the season names, which month each capture lands in, and every figure in the grid. The team, its matches and its figures are illustrative; the rules are the proposal.
1 · Setup: a season start for each team and each league, and no Seasons section
A season is always twelve months and ends the month before it starts, so the start month is the only thing asked. Seasons create themselves from FM's date: there is nothing to add, and the name comes from the calendar, so there is nothing to rename. A team's start locks once it has captures, because it decides where spells end. A league's does not: league captures have no spells, so changing it just re-files them by date.
Teams and squads
Leagues
2 · Data Capture: FM's date instead of the season and month chips
The date is read from FM when a capture starts, and it files the capture itself. The month strip that replaces the chips shows every capture this season, by date. Re-capturing on a date already held replaces it; any other date adds one. A step refuses to save if FM's date has moved since the capture began, since that would mix two days in one capture.
3 · A month grid: which month does a capture belong to?
Player Evolution's Form grid, one row per statistic and one column per month, each cell what changed since the column before. With any number of captures, a month's column shows its latest capture, and the views built for #224 show every one. What is left to decide is which month a capture belongs to, and the three rules on the switch give different answers for the captures you take today. The Matches row lists the games inside each column; it turns amber when a column is headed with a month whose games it does not hold.
Every habit, over the whole season
For the team above, every capture habit and time of day under both month rules: how many of the season's columns hold games from a month other than their heading, and where the season's first and last captures are filed.
B is the recommendation. It keeps what a month means today, how things stood at its end. Taken on the 1st, the way captures are taken now, A heads every month of the season with the month before's games, and B heads none of them wrongly. B's one slip is a game played on the 1st before a capture taken late that day: it lands in the month before. Captures on the last day of a month come out the same under both. What B costs is the first day of a season, which files under the last month of the season before.
Still open. Has FM rolled its season over by that first morning? If its figures are already zero on the 1st of the start month, that capture belongs to the new season and B needs an exception there. And A or B keep month names on every screen with the date under them, while C drops month names wherever a capture is shown: the most honest, but it reaches every heading in the app.