Repository navigation
Printing arrives, and a bug that could replace a table cell's text with the whole note is fixed. That bug affected 1.10.2 and earlier, so updating is recommended. 670 tests grew to 707. The .scrb format is unchanged.
Important fix
A table cell could take the whole note's text. After typing in a table cell, clicking the empty area of the note and pressing Ctrl+End replaced the cell's text with the entire note, and the next save kept it. The cell and the note were sharing the keyboard. Now clicking the note takes the cursor out of the cell first. Two smaller table fixes come with it: the first click on a new table now goes into the cell, and Tab in a cell no longer inserts a tab into the note.
Printing
File > Print (Ctrl+P, also in the command palette) prints the active note through the standard Windows print dialog. That means any printer Windows knows about works, including Microsoft Print to PDF and Universal Print. Rich text prints with its fonts, colors, lists, links and images. Plain text prints in the tab's font and size. Scrib uses the print engine built into Windows (the one WordPad uses), and the note never goes to a temporary file on the way.
Limitations:
- Tables and SVG images do not print yet. Scrib tells you before it prints.
- Printing an encrypted note asks first, because the printout is not encrypted. Windows keeps a copy in its print queue on disk until the printer is done, and cloud printers such as Universal Print upload it.
- A locked tab cannot be printed. Unlock it first.
Other changes
- Built with Flutter 3.47.7 (was 3.38.6), with the rich-text editor package moving from 11.5.0 to 11.6.0.
- Open, Save As, Insert Image and the default save folder now use Flutter's own file dialogs. They are the same Windows dialogs, and they now stay in front of the Scrib window until you close them.
Full details in the CHANGELOG.
Verifying this build
Releases are not code-signed, so Windows shows an unsigned-app warning. This release publishes a build provenance attestation, so the zip can be tied to the workflow run and commit that produced it:
gh attestation verify scrib-desktop-v1.11.0-windows-x64.zip --repo beeswaxpat/scrib-desktop
The attached SHA-256 is generated by the same workflow that builds the zip, so it detects transfer corruption but is not evidence of authenticity.
Download
scrib-desktop-v1.11.0-windows-x64.zip (sha256 checksum attached). Unzip and run scrib_desktop.exe. Windows 10 or later.