Bike 1.14 (152)

Tried v150. The truncation seems to work fine.

As for default settings, I manage to get the best results with the settings match quality = YES and duplicates = NO. This is because my project outline is milestone-based and I can quickly see which milestone each result falls into. Without seeing the ancestors, I can’t quite make that distinction.

One thing I noticed by accident is this: when searching for “beta reader”, I also get “beta readers” as close matches up top. But if I search for “beta readers”, then “beta reader” disappears altogether from search results. Not sure if this is a property of fuzzy search or not, but good for me to know :slight_smile:

Yes, this is expected. The “fuzzy” part in this case is that gaps are allowed when your search term matches against the text. But there is still requirement that all letters in your search term (and in same order) exist in the text to make a match.

I’ve started collapsing rows more to get a better high-level view of my document, and I’ve noticed that now when I navigate to a heading using cmd + P, even though it’s the only thing on my screen I have to manually un-fold it which I’m finding slightly tedious. The behaviour of “focus on a heading and keep it folded if it was” instead of “focus on a heading + unfold it no matter what” makes sense in the way that it preserves the pre-existing state, but I just noticed myself navigate to 10 different headings that were all collapsed, and un-folding the current one each time.

Though something super positive is that cmd + P is quickly becoming my most used shortcut!

1 Like

I agree this is a problem. I do plan to address, but just not in this release. This fall I will be adding outline filtering I think. That will require a bunch of code changes in the view layer (and elsewhere!) and will be a good time to make rows auto expand when focused as they do in TaskPaper.

2 Likes

Just posted 151. I think I will just keep in the various Choice View options. I cleaned that display up a little.

I also added Format > Add Link to Row. It uses the choice view to select a row, and then insert a link to that row. That also got me thinking about shortcuts, and I changed some things:

Added Command-K to create/edit link. Added Command-Shift-K to add link to row. Added Shift-Command-O to open link. And CHANGED Edit Formatting to use Command-E. That last one is a bit painful, but I think it makes sense long term.

1 Like

This is great! Really nice update.

I think I don’t understand the Add Link to Row. When I do that I get a little box next to the row. No link possibility. Maybe I am doing something wrong. See item 5: when I used shortcut it added that little box to the left of Starbucks. … all other shortcuts work just fine for me.

When happens when you use the menu item directly: Format > Add Link to Row?

It should:

  1. Show a choice palette where you can choose any row in your document.
  2. Add a link to that row to your current text selection.

When I use the menu item all works fine. Shortcut doesn’t work. … but I finally found the problem. I had a Keyboard Maestro macro for Bike that was the source of the conflict. Disabled KM macro and all is fine now.

2 Likes

I am experiencing some strange behavior. If I use the new palette (cmd-shift-K) to insert a link, when I click the resulting link, I receive an error (“Problem creating link: This linked document was found and opened, but associated row was not found.”) This occurs on a brand new Bike document from the builtin starting template.

I just discovered this myself… I think it only happens when linking to level one rows?

1 Like

Cool, and yes — I also see that it only seems to happen when linking to level one rows. (Incidentally, links created in the old way still work fine.)

1 Like

I’ve submitted this release to Apple. I plan to release on Monday, so still a little time if any bugs show up.

1 Like

2 posts were split to a new topic: Bike’s visual hierarchy

The bullets look skewed when the Bike note is opened in an external monitor. While, it looks perfect in the MacBook display.

External Monitor
1

MacBook Display
2

Possibly hardware-specific ?

(FWIW I’m not seeing that on an external Apple Studio Display)

1 Like

I think the issue is retina displays vrs non-retina displays. I know about this bug, tried to fix it once, and couldn’t find fix. Then forgot about it because my displays are retina! :slight_smile: I’ll try to fix again, but last time I remember running into a rather opaque brick wall when trying to figure out bug.

2 Likes

Things keep coming up. New plan is to release 1.14 tomorrow instead of today, which was instead of Monday! :slight_smile: Phew!

1 Like