Make Hatch better able to detect new printers

[Galen Charlton]

I observed on a Ubuntu box that Hatch as invoked via the Chrome extension did not automatically detect new printers added after Hatch was first started. I had to manually kill hatch as invoked by the extension, then reload the workstation printers page to see the new printer.

Discussion at https://stackoverflow.com/questions/38470568/javafx-doesnt-detect-changes-of-available-printers suggests that javafx.print.Print.getAllPrinters() may require the app to be restarted to pick up new printers; it also suggests that javax.print.PrintServiceLookup.lookupPrintServices() may be more dynamic.

On the other hand, I see that commit 6158abb2fbf1 removed use of javafx.print.PrintServiceLookup. Bill, do you remember why?

Hatch master

[Bill Erickson (berick)]

Hi Galen, I don't recall the reason for that change. At a glance, I'd guess the current approach simply requires less code.

BTW, I have confirmed that restarting Chrome causes Hatch to restart as well. I'm wondering if you tried that before having to manually kill Hatch?

[Galen Charlton (gmc)]

> BTW, I have confirmed that restarting Chrome causes Hatch to restart as
> well. I'm wondering if you tried that before having to manually kill
> Hatch?

Hmm, not all the way, just closing tabs that had invoked the
extension. I'll try restarting Chrome outright, although that (IMO)
just moves the issue to something that would have a documented
workaround.

[Bill Erickson (berick)]

I have confirmed on Windows that adding a new printer works when stopping Chrome, adding the printer, then restarting Chrome. Though stopping Chrome first is (almost certainly) not strictly necessary as long as it's restarted afterwards.