Hi,
I'm have Gtk2::Entry where users are expected to enter an XPath
expression. I would like to let the user know when an expression isn't
valid. I thought of using Pango markup but it seems very hard to do
with a Gtk2::Entry.
For the moment I can use a callback to 'changed' and set the markup
On Tue, 25 Nov 2008 12:47:43 +0100
Emmanuel Rodriguez [EMAIL PROTECTED] wrote:
Hi,
I'm have Gtk2::Entry where users are expected to enter an XPath
expression. I would like to let the user know when an expression isn't
valid. I thought of using Pango markup but it seems very hard to do
with a
Torsten Schoenfeld [EMAIL PROTECTED] writes:
Committed.
In the current cvs options.t fails for me with ... [the offending bytes
probably won't get through the mail]
not ok 19
# Failed test at /down/perl-gtk/perl-Glib/t/options.t line 151.
# got: 'blAñ'
#
Torsten Schoenfeld [EMAIL PROTECTED] writes:
* Initial standalone release.
A skip count typo when run on pango 1.20.5,
Index: PangoLayout.t
===
--- PangoLayout.t (revision 12)
+++ PangoLayout.t (working copy)
@@ -214,7 +214,7 @@
Torsten Schoenfeld [EMAIL PROTECTED] writes:
There's one thing that still isn't clear to me: what about the
gunichar issue? Your wrapper of g_param_value_validate uses
gperl_value_from_sv,
Yes, I basically followed g_object_set doing init_property_value() and
gperl_value_from_sv() once I
Torsten Schoenfeld [EMAIL PROTECTED] writes:
I don't know. The current get_default_property_value() certainly
allows custom param specs to provide their own get_default_value() and
have it called when appropriate.
I wondered after if that works, if a subclass would have to identify
itself to
On Tue, Nov 25, 2008 at 2:20 PM, zentara [EMAIL PROTECTED] wrote:
This is just a buggy prototype of what you might do.
Manually take control of the Entry and analyze it key-by-key,
probably with a regex for good xpath syntax,
and set the appropriate markup and entry text.
I tried using a
