touchy: replace deprecated font and colour overrides with CSS

[grandixximo]

GTK deprecated Gtk.Widget.override_font() and modify_fg() in 3.16. Touchy uses them throughout setfont() to set every display font and the per-coordinate DRO text colours, so it logs deprecation warnings.

This tags the widgets with style classes once and drives the fonts and colours from a single GtkCssProvider on the screen, rebuilt whenever a font or colour preference changes. A Pango font description is translated to CSS font properties, and stored colours are normalised through Gdk.RGBA. The rendered result is unchanged.

Tested with the ui-smoke touchy tests and by hand: the fonts render identically (buttons, DRO, tab labels, handwheel), and the per-coordinate DRO colours still apply (verified with rel/abs/dtg set to blue/red/green).

The modify_bg() calls in filechooser, listing and mdi are a separate selection-highlight pattern and left for a follow-up.

[hansu]

I would suggest to add property "name" to the widgets in the touchy.glade file and then add a block where all CSS styles are defined like I did in Gmoccapy:

linuxcnc/src/emc/usr_intf/gmoccapy/gmoccapy.glade

Line 1899 in 106519f

<property name="name">gcode_edit</property>

linuxcnc/src/emc/usr_intf/gmoccapy/gmoccapy.py

Lines 154 to 157 in 106519f

	#gcode_edit {
	padding: 3px;
	margin: 1px;
	}

This would not require so many changes in the touchy.py file I guess.

BUT for that the touchy.glade must first be converted to Gtk3. I tried this yesterday, but the result was not satisfactory - all the button were smaller and did not fill the space so I postponed that for the moment...

[grandixximo]

Thanks Hans. I looked at the gmoccapy approach and it's clean for fixed styling.

The difference in touchy is that its four display fonts (control, DRO, error, listing) and the DRO text colours are user preferences: set on the Preferences tab, saved to ~/.touchy_preferences, and changeable at runtime. So the CSS can't be a static block; it has to be generated from the current font descriptions and reloaded whenever a preference changes. That dynamic part (_font_to_css / _reload_font_css) is most of the diff and is needed regardless of how the widgets are selected.

The tagging itself reuses the font-group lists setfont() already had, so the net touchy.py change is small (mostly swapping override_font/modify_fg for one style class). I'm glad to use name properties in the glade instead of programmatic classes if you prefer; for per-group fonts a shared class is just more concise than naming every widget.

I agree the proper end state is a full GTK3 glade with the styling defined there, but that's the larger conversion you hit the button-sizing trouble with, so I scoped this PR to just removing the deprecated calls on the current glade. The rendered result is unchanged (verified the fonts and the rel/abs/dtg DRO colours).

Happy to go whichever way you and the maintainers prefer.

[hansu]

As far as I can see self._tag() is only applied to the widgets once in during init so I would prefer that as name property in the glade file. The rest is fine.

Happy to go whichever way you and the maintainers prefer.

Unfortunately I don't think we have a maintainer currently.

[hansu]

Just mark it here as "changes needed" to keep the overview =)

[hansu]

Move to name property in glade file (after merge of #4135)

[grandixximo]

Agreed on the order. I tested #4135 in a sim container and it renders correctly in GTK3 (the status grid is tidy now). At default Sans 18 it is still wider than a small screen until #4131's fitting is applied on top, which lines up with your 718x596, so #4135 then #4131 then #4133 makes sense.

For #4133 I'll move the widget identification into the glade as name properties on your converted file and keep the dynamic CSS generation for the user-set fonts and colours, then rebase both PRs onto #4135.

[grandixximo]

@hansu before I commit a large diff, one snag with moving the tags into the glade as name properties.

A widget has a single name, but the DRO readouts need two tags layered: the shared DRO font, plus an optional per-column colour (rel/abs/dtg) applied only when the user sets a non-default colour. The code does this with two style classes on one widget:

self._tag(w, "touchy_dro")   # font, always
self._tag(w, "touchy_rel")   # colour, only if non-default

name can't carry both, so a literal version has to collapse each DRO subgroup into one name whose rule repeats the font and adds the colour. It works, but it is less clean. Scale also matters: the tags cover ~150 widgets, so naming them all is a ~150-line glade diff replacing ~15 lines of code.

Two options:

• B (keep code tagging): per-group style classes applied once in setfont(). A widget can hold multiple classes, so the DRO font+colour layering stays natural and the grouping is a few readable loops. The deprecated override_font/modify_fg calls are gone either way.
• C (hybrid): name the simple single-tag groups (control, listing) in the glade, keep code tagging only for the DRO where the layering needs more than one class.

I lean to B for maintainability, but happy to do C if you would rather see control/listing declared in the glade. Which do you prefer?