Skip to content

TrestleBoard 1.4.0

Choose a tag to compare

@github-actions github-actions released this 10 Aug 22:42
· 22 commits to main since this release
The newsletter now knows which issue it is.

You set a cover date of 7 July, had a brother with a 3 July birthday,
and the birthday list would not fill in. The list was never the
problem. Nothing in the app had ever asked which month a newsletter was
for, so every newsletter started from a template quietly believed it was
January 2000, and the birthday list was dutifully looking for January
birthdays.

That one missing question was doing more damage than the birthday list:

- Exported PDFs were named " 2000-01.pdf" and carried "Trestle board
  2000-01" inside them.
- The email to the lodge went out as "Trestle Board - January 2000",
  with no lodge name in it.
- "What we said last year" searched for January 1999, found nothing, and
  told you your archive folder was empty -- after making you choose it.
- Starting next month's newsletter wiped the cover date instead of
  moving it on.
- The window title bar said "TrestleBoard -  - not saved yet".

What is different now:

- Starting a newsletter from a template opens the cover wizard and asks
  which issue it is for. Any month, any year -- it never guesses from
  today's date and never leaves it blank.
- "Start next month's newsletter" fills in next month for you, and still
  asks, so you can change it.
- A newsletter that has never been asked will ask before it does
  anything that depends on the answer, rather than getting it wrong
  quietly.
- The lodge name and the meeting rule you type on the cover now belong
  to the newsletter itself, so the email, the file name and next month's
  cover date all follow.

When the app cannot do something, it now says which month it means:
"Nobody in your address book has a birthday in January, which is the
month this issue is for." That sentence would have answered your
question in one glance.

Also fixed: a brand new newsletter now offers to fill in its empty
birthday list -- before, it only ever offered to update one it had
already filled in, which is part of why this looked like nothing
happening. An address book that will not open is no longer reported as
an empty address book. And the app no longer claims the birthday list
"already matches your address book" when it matched nobody at all.