Eduardo M KALINOWSKI wrote:
[...]
However, I find that solution not nice. The derived object structure
should be considered opaque, for example. I would like to connect the
signal to the derived object iself, not to widgets inside it:
g_signal_connect(G_OBJECT(derived_object), ...)
and have
Eduardo M KALINOWSKI wrote:
[...]
What is happening is that the user signal handler is being run only
after the default handler, even if g_signal_connect (not after) is used,
but it should happen before.
Hi,
what you're saying stikes me as odd; this is the declaration
of key-press-event
Tristan Van Berkom wrote:
Are you sure that the text view's handler gets called at all ?
in other words; are you sure you're returninig FALSE from
your Internal key handler ?
Yes, and as I matter of fact I removed this to test, and it did'nt
change a thing.
What happens is that if I connect
I'm using in my application a subclassed object (a subclass of HBox) that
contains a TextView widget (and some other things not relevant here).
What I'd like to do, with regard to key presses, is the following:
1. Almost all basic keys (letters, cursor movement, etc) should still be
Eduardo M Kalinowski wrote:
[...]
I've achieved capturing some specials keys, but letting everything
else work as normally in the TextView by connecting a handler to
a key-press-event of the TextView inside the derived widget's
implementation, but I have'nt discovered how to propagate keys
