On Thu, 6 Sep 2001, Lionel Ulmer wrote:
> My big problem now is that when I move the row displayed (using move_to),
> the row that is focused does NOT move with it. This means that when I later
> page-up or page-down, I move from the previously selected row and NOT from
> the position I see on the screen.
Yep, have the same problem. :/ James, any ideas?
> - be able to modify the 'focus_row' field of the GtkCList object. I do not
> know if this is possible via Python ?
Hmm, there is a toggle_focus_row; tried using it?
> - somehow 'grab' the page-up and page-down keys before they are sent to the
> CList and implement them myself.
This is doable (just catch key_press_event and emit_stop_by_name() in the
handler) but I'm not sure it would solve the problem.
> I really regret that there is no way to have a 'SELECTION_NONE' mode for the
> CList....
Hah! Me too. :) You can make it insensitive, you know, but that changes
the font colour.
> BTW, another misc. question : how can I get the parent of a widget in the
> widget hierarchy ?
FAQ alert, James! :)
widget['parent'] - yep, it's quite odd.
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
