Source code is printed with proportional font

[AESilky]

Using Cascadia Code in vscode editor for source, but the Print Preview and Print output is using a proportional font. Looked in the manual for a 'Font' setting, but it indicates that it will use the font set in VSCode and that only the size is configurable.

[PeterWone]

Are you using a Mac?

If so this is a known behaviour, osx font handling is broken for resolving fonts specified by name in CSS, for fonts not supplied by Apple. Try configuring vscode to use a core font (one supplied by apple) and if that works in preview and print then the problem is osx.

[AESilky]

I have noticed it on my Mac, but this was on my PC. In this example, in the editor the '=' all line up. It also doesn't use the tab size, as the comment blocks should also all line up (start and end). [image: image.png] I have Auto Update enabled and the change log indicates 1.6.0.

…

On Tue, May 5, 2026 at 3:58 PM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> Are you using a Mac? If so this is a known behaviour, osx font handling is broken for fonts not supplied by Apple. Try specifying a core font (one supplied by apple) and if that works in preview and print then the problem is osx. — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO73CX7YDG65IXJIN3D4ZJWYTAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOBTG42TONZWGU> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[AESilky]

I just tested on my Linux machine (Debian), and it's a problem on it as well.

…

On Wed, May 6, 2026 at 9:19 AM Ed Silky ***@***.***> wrote: I have noticed it on my Mac, but this was on my PC. In this example, in the editor the '=' all line up. It also doesn't use the tab size, as the comment blocks should also all line up (start and end). [image: image.png] I have Auto Update enabled and the change log indicates 1.6.0. On Tue, May 5, 2026 at 3:58 PM Peter Wone ***@***.***> wrote: > *PeterWone* left a comment (PDConSec/vsc-print#444) > <#444 (comment)> > > Are you using a Mac? > > If so this is a known behaviour, osx font handling is broken for fonts > not supplied by Apple. Try specifying a core font (one supplied by apple) > and if that works in preview and print then the problem is osx. > > — > Reply to this email directly, view it on GitHub > <#444 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AETPXO73CX7YDG65IXJIN3D4ZJWYTAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOBTG42TONZWGU> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[PeterWone]

As you can see it's working on this machine.

I thought perhaps it might be something like an unquoted font name containing spaces, but deliberately creating this situation on my system didn't cause a failure.

Take a look in your browser at the files delivered. Launch a preview, right-click on some of the source code and choose inspect, then take a look at the styling to see what font-family CSS is trying to apply.

You could also use network mode to take a look at the various files delivered. Start the preview, switch to network view then F5 refresh to populate the list of files delivered. Should look like this. You're interested in the settings.css file, which is dynamically generated from settings (yes, my imagination in naming is breathtaking).

Let me know whether the delivered CSS specifies Cascadia Code. If it does, there may be a browser error concerning font resolution.

[AESilky]

(no need to get imaginative on names if you don't have too ;-) The CSS specifies 'Cascadia Code', so something else is a problem. I'm using Chrome. I'll see what it does in a different browser. Hopefully I can figure it out. (I hate browser troubleshooting... that's why I'm an embedded developer!) [image: image.png]

…

On Thu, May 7, 2026 at 1:57 AM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> As you can see it's working on this machine. image.png (view on web) <https://github.com/user-attachments/assets/7087afbb-a0c6-4604-a626-5a55b1dc6bb7> I thought perhaps it might be something like an unquoted font name containing spaces, but deliberately creating this situation on my system didn't cause a failure. Take a look in your browser at the files delivered. Launch a preview, right-click on some of the source code and choose inspect, then take a look at the styling to see what font-family CSS is trying to apply. You could also use network mode to take a look at the various files delivered. Start the preview, switch to network view then F5 refresh to populate the list of files delivered. Should look like this. You're interested in the settings.css file, which is dynamically generated from settings (yes, my imagination in naming is breathtaking). image.png (view on web) <https://github.com/user-attachments/assets/df4d6408-07d6-4586-8337-7cab4abbe12a> Let me know whether the delivered CSS specifies Cascadia Code. If it does, there may be a browser error concerning font resolution. — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO2X6CAOXVCTU6ERUXT4ZRFYNAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJVGY2TMNRSGM> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[AESilky]

It's not just Chrome. This is Edge: [image: image.png] For reference, this is what it looks like in VS Code: [image: image.png] I understand, and understand why, the color scheme is different. The issue is just with the proportional font and tab size.

…

On Thu, May 7, 2026 at 10:11 AM Ed Silky ***@***.***> wrote: (no need to get imaginative on names if you don't have too ;-) The CSS specifies 'Cascadia Code', so something else is a problem. I'm using Chrome. I'll see what it does in a different browser. Hopefully I can figure it out. (I hate browser troubleshooting... that's why I'm an embedded developer!) [image: image.png] On Thu, May 7, 2026 at 1:57 AM Peter Wone ***@***.***> wrote: > *PeterWone* left a comment (PDConSec/vsc-print#444) > <#444 (comment)> > > As you can see it's working on this machine. > image.png (view on web) > <https://github.com/user-attachments/assets/7087afbb-a0c6-4604-a626-5a55b1dc6bb7> > > I thought perhaps it might be something like an unquoted font name > containing spaces, but deliberately creating this situation on my system > didn't cause a failure. > > Take a look in your browser at the files delivered. Launch a preview, > right-click on some of the source code and choose inspect, then take a look > at the styling to see what font-family CSS is trying to apply. > > You could also use network mode to take a look at the various files > delivered. Start the preview, switch to network view then F5 refresh to > populate the list of files delivered. Should look like this. You're > interested in the settings.css file, which is dynamically generated from > settings (yes, my imagination in naming is breathtaking). > image.png (view on web) > <https://github.com/user-attachments/assets/df4d6408-07d6-4586-8337-7cab4abbe12a> > > Let me know whether the delivered CSS specifies Cascadia Code. If it > does, there may be a browser error concerning font resolution. > > — > Reply to this email directly, view it on GitHub > <#444 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AETPXO2X6CAOXVCTU6ERUXT4ZRFYNAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJVGY2TMNRSGM> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[AESilky]

Found the problem - 'Cascadia Code' was misspelled: 'Cacadia Code' (missing 's') Thank you very much for helping out. I guess VS Code defaulted to a fixed font when it couldn't find the font and the browser defaulted to a proportional font. Maybe something to mention in the manual(?).

…

On Thu, May 7, 2026 at 10:19 AM Ed Silky ***@***.***> wrote: It's not just Chrome. This is Edge: [image: image.png] For reference, this is what it looks like in VS Code: [image: image.png] I understand, and understand why, the color scheme is different. The issue is just with the proportional font and tab size. On Thu, May 7, 2026 at 10:11 AM Ed Silky ***@***.***> wrote: > (no need to get imaginative on names if you don't have too ;-) > > The CSS specifies 'Cascadia Code', so something else is a problem. I'm > using Chrome. I'll see what it does in a different browser. Hopefully I can > figure it out. (I hate browser troubleshooting... that's why I'm an > embedded developer!) > > [image: image.png] > > On Thu, May 7, 2026 at 1:57 AM Peter Wone ***@***.***> > wrote: > >> *PeterWone* left a comment (PDConSec/vsc-print#444) >> <#444 (comment)> >> >> As you can see it's working on this machine. >> image.png (view on web) >> <https://github.com/user-attachments/assets/7087afbb-a0c6-4604-a626-5a55b1dc6bb7> >> >> I thought perhaps it might be something like an unquoted font name >> containing spaces, but deliberately creating this situation on my system >> didn't cause a failure. >> >> Take a look in your browser at the files delivered. Launch a preview, >> right-click on some of the source code and choose inspect, then take a look >> at the styling to see what font-family CSS is trying to apply. >> >> You could also use network mode to take a look at the various files >> delivered. Start the preview, switch to network view then F5 refresh to >> populate the list of files delivered. Should look like this. You're >> interested in the settings.css file, which is dynamically generated from >> settings (yes, my imagination in naming is breathtaking). >> image.png (view on web) >> <https://github.com/user-attachments/assets/df4d6408-07d6-4586-8337-7cab4abbe12a> >> >> Let me know whether the delivered CSS specifies Cascadia Code. If it >> does, there may be a browser error concerning font resolution. >> >> — >> Reply to this email directly, view it on GitHub >> <#444 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AETPXO2X6CAOXVCTU6ERUXT4ZRFYNAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJVGY2TMNRSGM> >> . >> Triage notifications on the go with GitHub Mobile for iOS >> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> >> or Android >> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >> >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[PeterWone]

I can look at validating fonts when the setting is updated.

[AESilky]

BTW - Your comment about the Mac only working correctly with Apple fonts is what led me to try different fonts on my PC and Linux box, which is how I discovered that Cascadia was misspelled. I tried a different fixed font and it worked, which I thought was interesting, so I went back to Cascadia Code and it worked. So I dug into things, looking at some of my other machines and the screen-shots and found the misspelling. I then purposely misspelled Cascadia, and once again the print preview went back to a proportional font. Thanks again.

…

On Sat, May 9, 2026 at 5:24 AM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> I can look at validating fonts when the setting is updated. — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO7VI3MG52XEVS72MUT4Z4PQ3AVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJSGUYTCMBRGU> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[PeterWone]

You had me worried when you said you had the same problem on Linux and Windows. That's the bulk of the user base, whereas Mac is a rounding error. I do a bit of embedded work myself, custom pump controllers, that sort of thing. I use Arduino Nanos, they're cheap and easy to get and I'm rarely building more than two of anything. Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________ From: Ed Silky ***@***.***> Sent: Sunday, May 10, 2026 3:11:15 AM To: PDConSec/vsc-print ***@***.***> Cc: Peter Wone ***@***.***>; Comment ***@***.***> Subject: Re: [PDConSec/vsc-print] Source code is printed with proportional font (Issue #444) [https://avatars.githubusercontent.com/u/19332027?s=20&v=4]AESilky left a comment (PDConSec/vsc-print#444)<#444 (comment)> BTW - Your comment about the Mac only working correctly with Apple fonts is what led me to try different fonts on my PC and Linux box, which is how I discovered that Cascadia was misspelled. I tried a different fixed font and it worked, which I thought was interesting, so I went back to Cascadia Code and it worked. So I dug into things, looking at some of my other machines and the screen-shots and found the misspelling. I then purposely misspelled Cascadia, and once again the print preview went back to a proportional font. Thanks again.

On Sat, May 9, 2026 at 5:24 AM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> I can look at validating fonts when the setting is updated. — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO7VI3MG52XEVS72MUT4Z4PQ3AVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJSGUYTCMBRGU> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#444 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABJ6QODMM3ADXICJE2SXZGL4Z5RDHAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJTGA4DCMRQGQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[AESilky]

The screenshot of the source I was trying to print was logic equations for an ATF1508 CPLD for a debugging board for retro Z80 systems. I do a lot of embedded work as well. My microcontroller of choice is the RP Pico (RP2040 and RP2350 based modules). I built a Mars rover the same size as the first Sojourner rover and a Pico does all the calculations and control of the 10 drive servos (6 traction and 4 steering). It accepts commands from an nvidia Jetson that does all the decision making (much more processing power than Sojourner had).

…

On Sat, May 9, 2026 at 4:53 PM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> You had me worried when you said you had the same problem on Linux and Windows. That's the bulk of the user base, whereas Mac is a rounding error. I do a bit of embedded work myself, custom pump controllers, that sort of thing. I use Arduino Nanos, they're cheap and easy to get and I'm rarely building more than two of anything. Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Ed Silky ***@***.***> Sent: Sunday, May 10, 2026 3:11:15 AM To: PDConSec/vsc-print ***@***.***> Cc: Peter Wone ***@***.***>; Comment ***@***.***> Subject: Re: [PDConSec/vsc-print] Source code is printed with proportional font (Issue #444) [https://avatars.githubusercontent.com/u/19332027?s=20&v=4]AESilky left a comment (PDConSec/vsc-print#444)< #444 (comment)> BTW - Your comment about the Mac only working correctly with Apple fonts is what led me to try different fonts on my PC and Linux box, which is how I discovered that Cascadia was misspelled. I tried a different fixed font and it worked, which I thought was interesting, so I went back to Cascadia Code and it worked. So I dug into things, looking at some of my other machines and the screen-shots and found the misspelling. I then purposely misspelled Cascadia, and once again the print preview went back to a proportional font. Thanks again. On Sat, May 9, 2026 at 5:24 AM Peter Wone ***@***.***> wrote: > *PeterWone* left a comment (PDConSec/vsc-print#444) > < #444 (comment)> > > I can look at validating fonts when the setting is updated. > > — > Reply to this email directly, view it on GitHub > < #444 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AETPXO7VI3MG52XEVS72MUT4Z4PQ3AVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJSGUYTCMBRGU> > . > Triage notifications on the go with GitHub Mobile for iOS > < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub< #444 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/ABJ6QODMM3ADXICJE2SXZGL4Z5RDHAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJTGA4DCMRQGQ>. Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO2RPHKKVUWWM6O5WY34Z7AHPAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJTHE4DGNJWGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[PeterWone]

What is it you like about the RP2040? My love of Arduinos has to do with price, availability, good dev tools and abundant drivers. Being able to get a carrier board with a socket and screw terms makes prototyping easy.

You'd laugh if you saw how rough some of my cobbled together monstrosities are. I discovered that double-hook industrial velcro is a good shock mount, so things stayed that way.

One of my planned projects is a spider leg with its own sensorium and reflexes. If I can get that right I'll build eight of them and a body to coordinate them and see whether locomotion can be expressed as a layered abstraction. But that's a one-day project.

[AESilky]

Many of my designs take great advantage of the PIO. The RP2050 has two instances with 4 state-machines each and the RP2350 has three instances with 4 state machines each. These can be used to off-load a lot of work from the CPU. The PIO state machines have access to all of the GPIO pins (to write, read, and/or change direction), the DMA can transfer to/from the PIO FIFOs, and the state machines can generate interrupts to the CPU. The CPU can also read/write the state machine FIFOs. In addition to the PIO, they have DMA, PMW/Counters, ADC, plus typical peripherals (2xSerial, 2xI2C, 2xSPI). The processor is also dual core. So, as an example... My Mars Rover (same size as the first, Sojourner rover) uses a single RP2350 to handle all the hardware control. It uses a PIO coupled with a DMA channel to receive RX data from a FrSKY Access SBUS receiver. The PIO takes care of receiving a complete SBUS packet (w/validation) and then interrupts the CPU to let it know that packet is ready. Another PIO instance scans a number of sensors (push buttons, perimeter touch, etc.) and makes the state bits available as a consolidated byte value to the CPU via a DMA transfer. The CPU can simply read the byte whenever it wants to get the current state of all the sensors. Another PIO SM decodes a rotary-encoder + push button for user input. Another PIO SM receives data from a sonar and a lidar ranger (changing baud from 115200 to 9600 and back as it switches between reading them), then it transfers the two distance values to memory via DMA, so the latest distances can be read from memory at any time by the CPU. One CPU calculates the drive and direction for the servos (6 drive and 4 steering), while the other handles the sensor and RC processing. One of the PWM is used to generate tones for audible feedback (radio connected, obstacle detected, battery low, etc.). One PWM/Counter generates a periodic 100 microsecond interrupt that is used for timing and the multitasking. If you want to take a look, that repo is: https://github.com/AESilky/ack-ack/tree/master Arduino probably has more external device driver support, but for my projects I typically write all my own drivers (that is part of the enjoyment I get out of the projects). However, in a few cases I've wanted a quick project done and needed a driver that wasn't available for the Pico. In those cases I found that I could pretty quickly convert an Arduino driver for use on the Pico. I've generated a pretty good collection of drivers. There are, however, quite a number of device drivers available for Pico if you do a bit of searching. Another project that I don't think you could do with an Arduino (at least not a single one) is this full retro serial terminal: https://github.com/AESilky/RP2040-VersaTerm I do my development in VS Code, and debug using the SWD port on the Pico connected with GDP and OpenOCD.

…

-Ed

On Mon, May 11, 2026 at 2:59 PM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> What is it you like about the RP2040? My love of Arduinos has to do with good dev tools and abundant drivers. — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO46AE3VFFJ3SNDTKSD42JEKTAVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMRVGUYDKNZTHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[PeterWone]

How did you achieve that build quality? That's not a hand-made board.

[AESilky]

Hi Peter, I build a lot, and I've done it for many years. For SMD I have jeweler's glasses, very-very small stainless steel tweezers (so they aren't magnetic), and a small IR reflow oven. Here are a few of my other boards: [image: MK-KS-IF-MkV.jpg] [image: SD-PGMR-wod.jpg] [image: SD-Scores-test.jpg] [image: SD-ZMB_sys.jpg] As you can see (in the last one), occasionally design errors occur and need to be fixed by an extra chip and some wire-wrap wire. ;-) -Ed

…

On Tue, May 19, 2026 at 2:59 PM Peter Wone ***@***.***> wrote: *PeterWone* left a comment (PDConSec/vsc-print#444) <#444 (comment)> How did you achieve that build quality? That's not a hand-made board. — Reply to this email directly, view it on GitHub <#444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETPXO4ETAS7G4GVA4VTS6T43TKN3AVCNFSM6AAAAACYSE6QEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOJSGQYDIMZSGE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>