Few more consistency tweaks and documentation shortening. Think I’m done messing now, but I may have said that last release also.
I think those must be old themes that are in some now incompatible format. Go to Session > Themes > Open Themes Folder and delete contents if any.
Also your log says skipping old !bike core extension. You can fix that by going to Bike > Extensions Explorer. Click the folder icon in the toolbar, and then delete extension named !bike.
Thanks! That sorted everything.
I’ve been thinking about a couple of potential quality of life improvements.
bike://nEuBPzo5/NYl) seem to function only as intra-file links, meaning if I am in file A.md I can use it to navigate to different rows. But if I am in file B.md and I paste a link to a row in A.md, it doesn’t do anything. I think it would be nice to have, as sometimes I’ve written something in one file, and I want a way in another file (either a Bike file or somewhere else) to link to this Bike file/row. So ideally bike links would function as inter-file and even inter*-application* links.Thanks for considering these items.
Working here between files, and from other apps.
You’ve checked Bike > Settings > Sandbox ?
Expanding on what @complexpoint says, this should all already be working. The way it works is links are formatted as bike://<outlineid>/<rowid>. When Bike resolves a link it first looks to see if outline with matching ID is open. And matches link to that. I would think the link should be working for you currently … when you have both documents open?
You can ready more about sandbox settings and fixes here:
I don’t think I will add this now. It would require rethinking of UI sizes, etc. I will make sure that items have proper tooltips though, so when you mouse over you’ll see command name.
I think this already exists in the form of Go > Go to Command (Command-Shift-P). That list should include all Bike commands, including those in the window menu.
Is a license required to format text now, or is this a possible regression?
@complexpoint @jessegrosjean re. the Bike links,
I tried creating a minimal reproducible example; please see attached for a screen recording. I have two files, both open in Bike and both in the default iCloud directory. Let me know if you see anything I’m doing wrong.
I believe this has always been the case, or at least it has been the case for a long time in Bike 1.x.
Thanks, that helped a lot.
That is a bit buggy, but I think the link is actually working. What is not working is the linked to document tab (or window if the windows are not grouped) isn’t activated. So in your example clicking on the link in B is focusing the row in A, but I need to update selected tab.
I’ll try to fix that soon.
The previous previews allowed text formatting.
I just checked back to 284 and they all required license for Command-B to make text bold. I did connect up some license validation a month or two back, but I don’t think there has been any changes too recently.
Another possibly, are you sure you didn’t already have a license? If you purchased it a year ago, then one of these recent release could require a renewal, and that would explain the change in behavior.
I don’t have a license but will purchase one soon. Till then, I can live without the formatting.
Slight visual bug: If you create an unordered list with no text, and a child foo, it looks like this:
If you then put the cursor after the •, it looks like this (arrow overlaps the placeholder text):
Another small one: When I press enter, the Paragraph text abruptly turns zero-opacity and fades in:
And another small oddity: If you indent 4 times, then put this in a code block: abcdefg: [ { ab, abcde, abcdefghij }, ... ]it will span two lines (actual size, window full width on a 16” MBP)
If you then add another character to abcdefghij, it jumps back to one line, so the longer text makes it go back to one line even though it was previously on two lines):
Edit: I also noticed that when I unfocus the window while a placeholder text is visible, it shrinks. Not sure if intentional but here’s a screenshot:
Edit 2: Maybe intentional, but I wonder if it would make sense for the left edge to be lined up across lines for multi-line highlights.
