Hi, (sorry for the format but on weekends I have to use horrible webmail)
>Apparently this is my problem. If I call gtk.TreeView.__init__,
>nothing happens, and the new signal is not usable (Control-Up >does the
>same as Up in itself, and if I try to emit the signal with
>treeview.emit(...) I get a "TypeError: unknown signal name".) If >I
>leave out the call to gtk.TreeView.__init__(), I get a completly >blank
>widget. (Which does have the new signal as I can with >treeview.emit())
Try changing the __init__ method to:
def __init__(self, model, *a, **kw):
self.__gobject_init__()
self.set_model(model)
This way you are not calling gtk.TreeView.__init__ (so you register your signal
properly) and your model is set.
Anyway, I run into other problem: when I type CTRL+Up the signal is emitted but this
is what i get:
(widgettest.py:2227): Gtk-WARNING **: gtk_binding_entry_activate(): binding
"__main__+HnbTreeView::<Control>Up": signal "move-to-sibling" in the
`__main__+HnbTreeView' class ancestry cannot be used for action emissions
No clue about this but I never worked on key bindings before so It's probably lack of
knowledge here.
Lorenzo
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
