On Tue, Jan 14, 2003 at 10:20:32PM +0000, Andrew S. Townley wrote: > This time I've included an example of what I'm trying to do. It serves > to illustrate both my previous "double selection signal" issue as well > as something different.
One thing is that you're passing an integer as a path when (I think) you should be passing in a tuple (but pygtk doesn't seem to mind <shrug>). However, using a tuple doesn't seem to make a difference. I know I've gotten scroll_to_cell to work just fine in my own app, but I can't see what's going wrong here. > To watch the first one, make sure the checkbox isn't checked, then click > load. Choose a row, say the 4th one, and you'll see the double signals. I think this is the correct behavior for the first time something is selected. But then I'm never sure what the intentions of the gtk authors really are. > The second one seems to be that the treeview isn't capable of scrolling > to a set position initially after it is loaded. Subsequent requests > after reload work, but the first one never does. I'm guessing that it > has to do with the "phantom" selection of row 0. To watch this one > (unless it randomly selects 0 or something), run test2.py and click the > checkbox before clicking load. Subsequent reloads always seem to work, > but it is just the first one. > Any ideas? Nope. I don't why it's not working. Dave Cook _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
