Bug#518813: gucharmap: Focussing the font selection box not possible anymore

[Christian Ohm]

On Tuesday, 24 March 2009 at 12:32, Josselin Mouette wrote:
> Le lundi 23 mars 2009 à 23:18 +0100, Christian Ohm a écrit :
> > On Monday, 23 March 2009 at 22:32, Josselin Mouette wrote:
> > > It sounds to me, given how GTK+ works, that this change is intentional. 
> > 
> > Yes, it might even be a change in GTK and not gucharmap, so that "secondary"
> > widgets don't get focused anymore (I don't remember if I updated GTK at the
> > same time or not).
> 
> No, the change is in gucharmap; that’s not normally how GTK+ works.
> 
> > > If you can suggest an improvement on the behavior, feel free to provide
> > > ideas, but IMHO it would be a regression to just go back to the 2.22
> > > behavior.
> > 
> > Well, to me the current behaviour is a regression (gucharmap's homepage even
> > lists "switch among fonts quickly" as one of its features). The current
> > behaviour requires a "aim-click-aim-click" sequence (or
> > "click-downarrow-enter", one action less, but easier to get wrong since all
> > three are different, and involve both mouse and keyboard). An (optional) font
> > list box to the left (or right?) similar to the script/codeblock column might
> > be a good solution, if the former widget behaviour cannot be restored or is
> > deemed undesirable.
> 
> Frankly, if you want to debate that, please do so directly with the
> upstream authors. I don’t think we’re going to diverge from upstream for
> such a small and unclear issue.

Frankly, if you don't want ideas, then don't ask for them. I just wanted to
report a regression in the new version, as long as it's solved I don't care
how.

Best regards,
Christian Ohm