- “Hide outline controls when typing” is now three checkboxes
- Moved the editor toggles from General to Appearance settings
- Row links can now name a row by persistent id, session id, or row number
- Fixed an attachment not animating when you deleted the character before it
- Fixed Autocorrect settings showing stale checkboxes after Reset settings
- Fixed Save As freezing on OPML documents
- Fixed modifier keys getting stuck
2 Likes
I’m back at trying Bike again, now. Great progress!
Tabs don’t work for me — is this disabled or something? I can show the tab bar, but I can’t make new tabs or add other documents to it. (And is it supposed to be styleable by themes?)
Hopefully this is the last time I have to re-write my editor style..? 
I started with the theme, though, and the new, more robust system, looks good. Some comments/questions from working on it yesterday:
1)
While trying out the glass effects, I added this to the sidebar:
"fill": {
"type": "glass",
"style": "regular"}
However, it then gets a weird blue artifact up top, like there’s something blue behind there. Even if there is no background colour etc.
2)
I was a bit confused by how spelling and grammar is just colours, while links use an underline styling. It seems to me that spelling et al. uses "thick": true, and I wish I could have it be single (but either way, I think it should use the same logic as other elements that are underlines).
3)
I wish adding background to codeblocks would (or at least could) use the same logic as when you’re selecting blocks. Here is the background colour it gets now:
But selecting gives a more “blocky” look:
4)
Not very important, but I tried to add corner radius to the bottom left of the editor window, and it didn’t do anything. Also, I’ve noticed that some apps can make the entire window transparent, to show things beneath (from the OS). I think this should be possible to experiment with on Bike as well. (But I guess blur is needed, in addition to the glass effects..?)
5)
I tried to give a slight colour change to "emphasis" — but this seemed to also affect things like blockquotes (that are set to be ["italic"]). I’m not sure it should? Also, I wasn’t able to style bold+italics. Maybe that should be a third thing..? How is that handled?
Sorry for comments on things that are probably not what you are working on right now! But will look into things like attachments later. 
I don’t know why BikePreviewExtension is doing this.
First time I saw this, BikePreviewExtension was at 64%
I restarted Bike, and BikePreviewExtension ran > 40% (the above screenshot)
I re-restarted Bike, and BikePreviewExtension is currently at 28%.
Throughout, Bike itself runs at very low CPU (≤ 1%)
1 Like
Sample of BikePreviewExtension (Finder).txt (1.5 MB)
I got Claude to diagnose an Activity Monitor sample:
The key details: sustained 40–60% CPU, 536MB RAM, process stuck in JS/ObjC callback loop during
_sendViewDidLoad, triggered by Finder Quick Look preview generation.
Option-Command-N should create a new tab.
Tabs are not themeable, other then the fact that they are a bit transparent and window background material will show through.
I think this is just part of the glass effect. Takes color from outside Bike’s window and reflects it in the glass. If we are talking about the same thing, if you move your Bike window to some other location on the screen the effect will change.
Generally it’s hard to make glass effect fit in well in Bike’s theme. Best option I think is to use glass effect for entire window background. Then use a fill effect for places (like editor) where you don’t want it.
I don’t think that links use an underline styling? They are just blue text? Spelling and Grammar are created via custom decorations (in the stylesheet), so that’s why theme is just inputting a color. I’m leaving it that way because I may go back to Bike 1’s zigzag display.
I will try to get to the rest of these later, might be next week! Thanks for the feedback… and generally for your theme needs it might make sense to use a combination of a theme and custom Bike style like you had before.
Thanks, I think I have this fixed for next release.