aleleba/vectorcraft
1
0
Fork 0
mirror of https://github.com/storytold/vectorcraft.git synced 2026-10-24 09:46:59 -06:00
Code Issues Packages Projects Releases Wiki Activity

Docs: the Print section describes printing through the system's print service

Browse Source 
The Print section of docs/mcp.md said that File → Print writes the job
as a print-ready PDF and that there is no printer driver. The desktop
app sends the PDF to the system's print service, the web build opens
the browser's print dialog on it, and the PDF File entry in the
Printer list saves it. The section now says so, points to Printing,
and marks the `file.print` reply that follows as the headless one.
This commit is contained in:
dotCooCoo
2026-10-16 02:56:34 +07:00
committed by bflatastic
parent 4a1323ad07
commit 513685a221
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/mcp.md
+4 -2
View File
@@ -2477,8 +2477,10 @@ Screens doesn't write EPS.
## Print
File → Print writes the job as a print-ready PDF (there is no printer driver): each page is a sheet of the chosen
paper. `file.print {settings?, path?}` → `{pages, path | dataBase64, bytes, warnings}`; `print.preview {settings?}`
File → Print lays the job out as a print-ready PDF, in which each page is a sheet of the chosen paper. The desktop app
sends the PDF to the system's print service, and the web build opens the browser's print dialog on it. With PDF File
picked as the printer, File → Print saves the PDF instead (see Printing). Headless, `file.print {settings?, path?}` →
`{pages, path | dataBase64, bytes, warnings}`; `print.preview {settings?}`
answers what it would print without writing it: `{pages (copies included), sheets: [{artboard, tile?, ink?, width,
height, orientation, scale}] (one copy, in order), tiles: [{artboard, columns, rows, printed, tiles}] (document
space), inks: [{name, spot, print, frequency, angle}], warnings, settings}`. `print.setup {settings?}` saves the