Control-click to show context menu with edit options
Added .html support when copying from Bike
Added .rtf support when pasting into Bike
Changed indentation to char width increments
Changed selection to extend to contain inserted text
Fixed ensuring unique root ids for all open documents
Fixed cases where drawing was not at correct pixel boundary
Fixed detect links to work when link is not at start of line
Fixed bike link resolution problem when multiple documents are open
Fixed ensuring text formatting isn’t allowed in plain text formats
Fixed paste to add link to selected text to only add link if pasted text is a link
Fixed crash when interacting with RTL text, crash gone, still need more work to better support RTL text
Fixed detected link to not override underlying link value. This handles case when a link label is also recognized as a link
Fixed .bike encoding to not adding spaces between format runs when viewed in web browser. Pretty printing is now only applied to outer elements in the file format, but not to the <p> element and its contents.
To get preview releases through Bike’s software update select: Bike > Preferences > General > Include “preview” releases.
This is fantastic! I can now simply copy Bike outlines to Apple Mail or Microsoft Word! My previous workaround (opening the .bike file in Safari to copy the generated HTML) is no longer necessary
It became OK when the Font was changed to mono in Preferences, but when the Font is a proportional type such as System and the format is set to Code, the indentation between Code Rows remains misaligned.
I don’t think that would make much difference. You start a row with “m” instead of “I” in a proportional font (for example) then the chars are just not going to line up I think.
The current indentation spacing is calculated as:
Measure width of SPACE
Multiply that SPACE width until the value is >= 28.
I see what you mean that the “code” marks mess up the alignment, but I’m not sure that I want to address that now. Even if I correct for code marks then there is still the link button… which is a different width then the code marks and can also create the same problem.
A possible solution would be to make those inserted chars also always a multiple of SPACE char width, I might do that later, but I think it will require testing and tweaking to make it all look right and I don’t want to get into that right now.
I’m adding a note about this in my long term feature list, but will leave as is for now.