qet-mcp README: the preset note says frame, not PDF page

The note the op returns reads "...; frame 1223.25 x 791.25 pt"; the README
quoted it as "PDF page".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ispyisail
2026-10-03 07:51:44 +13:00
parent 580cbb1cb1
commit 8bbdafe2e4
+6 -5
View File
@@ -571,11 +571,12 @@ Python, plus the hang guard on `addConductor` and the database refresh in
stay whole numbers, because the folio properties panel edits them in stay whole numbers, because the folio properties panel edits them in
whole pixels and would round a fraction off the first time it was whole pixels and would round a fraction off the first time it was
opened; so the page can come out up to 0.75 pt short of the sheet a opened; so the page can come out up to 0.75 pt short of the sheet a
side. The op's `note` says what it chose and the page a PDF export side. The op's `note` says what it chose and the size of the frame a PDF
writes, e.g. `23 columns of 70, 12 rows of 82; PDF page 1223.25 x export measures, e.g. `23 columns of 70, 12 rows of 82; frame 1223.25 x
791.25 pt` for tabloid landscape from a new folio. (The PDF export makes 791.25 pt` for tabloid landscape from a new folio. (The PDF export
the page the frame and title block plus its one-pixel line, at 96 pixels measures the frame and title block plus its one-pixel line, at 96 pixels
an inch: 0.75 pt a pixel.) Needs `qet.folioPresets()` in the build. an inch: 0.75 pt a pixel, and writes it on the standard sheet it is
within 3 pt of.) Needs `qet.folioPresets()` in the build.
- **The `wiring` export names unnamed terminals.** Most shipped symbols - **The `wiring` export names unnamed terminals.** Most shipped symbols
leave their terminals unnamed, so `from_terminal`/`to_terminal` are often leave their terminals unnamed, so `from_terminal`/`to_terminal` are often
empty. Each row also ends with `from_terminal_index`, empty. Each row also ends with `from_terminal_index`,