Re: [pygtk] TreeView/cell/signals - SOLVED
> If I understand your question I don't think that you can prevent the > Entry that is used as the CellEditable for the CellRendererText from > closing when activated. You can only prevent the edits from being > applied which is the default. thanks for your answer that awoke my brain... Really you *can* stop the process, what you cannot do is stopping from withing 'edited' callback. You must be in 'remove-widget' callback. I ended up using some variables to define the validation-state during 'edited' callback, I can also start completion with EntryCompletion. It wouldn't normally even popup as the widget is deemed to be removed, but I intercept it with 'remove_widget_cb' that returns True to stop the process. It's up to you to prevent opening several different cell editable at that point... sandro *:-) -- Sandro Dentella *:-) http://sqlkit.argolinux.orgSQLkit home page - PyGTK/python/sqlalchemy ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] TreeView/cell/signals
Alessandro Dentella wrote: > ... the same problem, a different point of view... > > If I enter a CellRendererText in editing mode I can press return and the > mode switched and signal 'edited'is emitted. > > Who is responsable for that? I guess is the editable as I can't imagine > anything else... but how can I be sure? I mean is there a way to "listen all > signals" and who is emitting them? > > Which is the signal emitted? > > What can I do from within the 'edited' callback to stop switching from > editing mode? > > sandro > > > The signals are described in the Reference Manual but sometimes can be hard to find. The devhelp application can help find them because it provides a search mode. If I understand your question I don't think that you can prevent the Entry that is used as the CellEditable for the CellRendererText from closing when activated. You can only prevent the edits from being applied which is the default. John John ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
[pygtk] TreeView/cell/signals
... the same problem, a different point of view... If I enter a CellRendererText in editing mode I can press return and the mode switched and signal 'edited'is emitted. Who is responsable for that? I guess is the editable as I can't imagine anything else... but how can I be sure? I mean is there a way to "listen all signals" and who is emitting them? Which is the signal emitted? What can I do from within the 'edited' callback to stop switching from editing mode? sandro -- Sandro Dentella *:-) http://sqlkit.argolinux.orgSQLkit home page - PyGTK/python/sqlalchemy ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
