r44677 | gpz | 2023-11-12 18:12:26 +0000 (Sun, 12 Nov 2023) | 1 line
add missing includes
------------------------------------------------------------------------
r44676 | compyx | 2023-11-11 15:26:37 +0000 (Sat, 11 Nov 2023) | 5 lines
Gtk3: printer output mode widget: be consistent: use strings, not integers
The "Printer[4|5|6|Userport]Output" resources are strings, so the UI should also
use strings "text" and "graphics" to select output mode, not 0 or 1.
------------------------------------------------------------------------
r44675 | compyx | 2023-11-11 14:48:16 +0000 (Sat, 11 Nov 2023) | 2 lines
Replace local `PRNR_*` device index defines with `PRINTER_*` defines from `printer.h`
------------------------------------------------------------------------
r44674 | compyx | 2023-11-11 14:42:24 +0000 (Sat, 11 Nov 2023) | 5 lines
Gtk3: Prevent selecting invalid printer driver and output mode combinations
Grey-out text/graphics mode selection when a printer/plotter doesn't support
both modes and auto-select the only valid mode, if a driver is selected.
------------------------------------------------------------------------
r44673 | compyx | 2023-11-11 10:07:05 +0000 (Sat, 11 Nov 2023) | 22 lines
Printer: make drivers register some properties
Instead of relying on fixed arrays of driver names to check a property of a
printer driver, make the drivers responsible for registering their properties,
so we can inspect at runtime what those properties are (both for core and UI
code).
Properties added to the `driver_select_t` object are:
- Device type (printer and/or plotter)
- Device name to use in the UI
- Device can be connected through IEC bus
- Device can be connected through IEEE-488 bus
- Device can be connected through userport
- Device supports text output
- Device supports graphics output
Make heap-allocated copies of the `drv_name` and `ui_name` members so
registering the drivers can be made more flexible.
The Gtk3 UI uses the registered drivers list to generate driver lists per
device (4, 5, 6, userport) instead of relying on its own list of supported
drivers per device.
------------------------------------------------------------------------
