This is, I think, a design decision of GTK (mainly due to accessibility
concerns). See issue post here:
https://gitlab.gnome.org/GNOME/gtk/-/issues/270#note_394060.
It may be possible to implement the keypress hack you described, but you may be
compromising accessibility for aesthetics.
Best,
> *** can not find package cairo >= 1.0.0
You need to have the underlying C libraries installed in order to use the Perl
wrappers. Here is a good place to start:
https://www.gtk.org/docs/installations/windows
Note that if you really want/need to use Gtk2 rather than Gtk3, you need to
change
On Mon, Oct 18, 2021 at 08:39:36PM +1100, Daniel Kasak via gtk-perl-list wrote:
> It's not really clear if there's something *else* I'm
> supposed to do to these strings coming out of the DB or not?
Typically you need to tell Perl to treat them as UTF-8. Without knowing exactly
how you're
In the case of your example script, you need 'use utf8;' in the preamble. This
fixes handling of the hard-coded unicode characters in the script -- it won't
necessarily fix the issue with the strings coming from your database. Are you
certain they are being stored in the database correctly?
On Fri, Sep 13, 2019 at 12:20:11PM +0200, Torsten Schoenfeld wrote:
> > The module uses Glib::Object::Introspection to generate the bindings, and
> > I'm unsure if the fix for this bug should be in G::O::I or some sort of
> > override in the Poppler module. Getting too deep into the glib/XS
Hello,
A bug related to memory management was reported for the Poppler bindings I am
maintaining:
https://rt.cpan.org/Public/Bug/Display.html?id=130280
The module uses Glib::Object::Introspection to generate the bindings, and I'm
unsure if the fix for this bug should be in G::O::I or some
