Bike 2.0 (Preview 291)

Bike Outliner Releases
21

The pie chart is incredibly welcome! Now I can see at a glance where I still have open todos. Combined with the calendar dragging feature, this is super useful.

Screenshot 2026-07-30 at 11.15.05
Screenshot 2026-07-30 at 11.15.05464×950 81.8 KB

Is there a good way I can add those ISO @ids to my legacy dates or should I go with the AI/python route?

22

Good to hear!

You mean so they associate with the Calendar days? There isn’t any build in way, so you’ll have to do that manually… but were you just not using the calendar to generate dates before? It shouldn’t be that those ids changed, unless it was accidental on my part somehow.

23

Yes! But some early dates I created manually before I started using the calendar (didn’t like deleting the year/month root, I keep my dates in a single 2026 file), so they have a regular row @id.

I’m experiencing some trouble with row links:

Screenshot 2026-07-30 at 12.53.56
Screenshot 2026-07-30 at 12.53.56476×552 66.2 KB

Screenshot 2026-07-30 at 12.56.47
Screenshot 2026-07-30 at 12.56.47468×420 41.2 KB

The linked document is inside Bike’s iCloud folder and it actually opens but then throws these errors.

What I’m doing:

  1. Select row in linked document
  2. Edit → Copy → Copy Row Link
  3. Paste row link into main document
  4. Verify link works (it does)
  5. Close linked document
  6. Use link in main document

I think I remember from some earlier conversations that the linked document needs to be open for the link to actually work, but…after step 4, Bike does open the document but still throws errors when I try to use the link. Am I doing something wrong?

EDIT: Weirdly, this doesn’t happen if I save linked document after copying row link and before closing it.

1 Like
24

@Gorgonzola Thanks, I’ll get this fixed for next release.

Ah, that’s the key. I think the issue is that:

  • row ids are now only created on demand
  • I didn’t want that id creation process to be undoable
  • but a side effect was that row id creation didn’t dirty document and require a new save
  • so the id was getting created, but not saved automatically and so it broke when later trying to resolve that row id.
2 Likes
25

I believe this is fixed in:

1 Like