asom...@gmail.com schreef:
> I see. AFAIK a treeview won't emit any signal on a double click.
>
What about this?
treeview.connect("button-press-event", treeview_clicked)
def treeview_clicked(widget, event):
if event.button == 1 and event.type == gtk.gdk._2BUTTON_PRESS:
print "Double clicked on treeview"
button-press-event is inherited from gtk.Widget.
Works fine in my program.
Timo
> Maybe you could define your own widget that inherits from both
> gtk.Button and gtk.TreeView so you can get the clicked signal. Then
> you would have to use something like
> gtk.TreeView.widget_to_tree_coords on the event's coordinates to get
> something useful. Just a thought.
> -Alan
>
> On Fri, Aug 14, 2009 at 12:22 PM, Tobias Weber<t...@celvina.de> wrote:
>
>> On 14.08.2009, at 19:29, asom...@gmail.com wrote:
>>
>>
>>> Try connecting to the 'edited' signal of the CellRendererText
>>>
>> That's emitted after editing stops. I need an alternative to editing.
>> Like a file manager: slow double click edits, fast double click
>> launches.
>> _______________________________________________
>> pygtk mailing list pygtk@daa.com.au
>> http://www.daa.com.au/mailman/listinfo/pygtk
>> Read the PyGTK FAQ: http://faq.pygtk.org/
>>
>>
> _______________________________________________
> pygtk mailing list pygtk@daa.com.au
> http://www.daa.com.au/mailman/listinfo/pygtk
> Read the PyGTK FAQ: http://faq.pygtk.org/
>
_______________________________________________
pygtk mailing list pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/
