RE: [gtkmm] refTreeSelection->select(iter);

[Murray Cumming Comneon com]

> From: danny van elsen [mailto:danny_van_elsen hotmail com] 
> thanks for the hint... but it finally dawned upon me that the 
> row selected 
> was always at the position that got double clicked.
> 
> so probably some trace of the double click still is hanging 
> about, forcing 
> the selection of the wrong row.
> 
> if I make the callback respond to a key press, then
> gui_tv->scroll_to_row(p, 0.5);
> gui_tv->set_cursor(p, *pColumn);
> does the job...

Maybe it was set_cursor() that I was remembering. I remembered that there
was an extra step. This is probably what I do In Glom. I do suggest you look
at my source code, like I said.

> since I'm not really familiar with all the details of gtk:
> what would be the best way of reserving the double click for 
> my callback 
> only?

I'm not sure if that question makes sense. But you might get more useful
information on gtk-list gnome org  For now I assume there's a good reason
for a scroll_to_row() and set_cursor() being separate.

Murray Cumming
murrayc usa net
www.murrayc.com