GitLab

Going forward, g_object_ref will have a properly typed result.

*sigh*

https://bugzilla.gnome.org/show_bug.cgi?id=790534

Themes use "*" here and there so "fallback" is useless.  We might need
multiple css files at different priorities eventually.

This makes the buttons scale with font size.

Interesting conclusions:

Computing sqrt(2pi) as double yields the right value?  no
Computing sqrt(2)*sqrt(pi) as double yields the right value?  yes
Computing 1/sqrt(2pi) as double yields the right value?  yes

So 1/sqrt(2pi) is correct even though sqrt(2pi) is not.

...because then they will do it independently for x and y directions.

This is for gtk+ 3.20+.  It doesn't do much yet, but it is possible to
play with some thing, for example

rotationselector canvas {
  font-size: 2pt;
}

This kills "unused" and "set, but unused" warnings.  Only deprecation
warnings and #warning are left.

This simplifies the code by using a gobject data item to store the color
instead of forcing that information into the gui.  The code is simpler
and less likely to break.

This might also fix a problem with history.  The activate handler will
now get the color from the same place, not the color the swatch had when
created.

This answers the question whether those constants can be computed
accurately using double math.  Evidently they can.