Re: new GtkTreeModelFilter() vs. GtkTreeModel::filter_new()

From: Date: Sat, 24 Jun 2006 17:43:10 +0000
Subject: Re: new GtkTreeModelFilter() vs. GtkTreeModel::filter_new()
References: 1  Groups: php.gtk.dev 
Request: Send a blank email to php-gtk-dev+get-3149@lists.php.net to get a copy of this message
I don't think we need filter_new(). Of course, Steph might bite my head off for not conforming to Gtk+ API precisely, but that's a risk I'm willing to take. :) -Andrei On Jun 12, 2006, at 10:04 AM, Christian Weiske wrote:
Hello all, You might have noticed that there was a little confusion on my side about the question how to instatiate GtkTreeModelFilter. I committed the patch for the constructor some days ago. It requires a model and a path as parameter. Unfortunately (or luckily), GtkTreeModel::filter_new did also exist. Both use the same implementation currently (causing the latter to fail), and I want to ask if we just want to drop the second or keep it. If we want to keep it, I need to add a working implementation of GtkTreeModel::filter_new. --Regards/MfG, Christian Weiske


« previous php.gtk.dev (#3149) next »