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

We had this discussion before, but since I can't even remember why we did, what the arguments were or what the outcome was I guess your head's safe for now :) ----- Original Message ----- From: "Andrei Zmievski" <andrei@gravitonic.com> To: "Christian Weiske" <cweiske@cweiske.de> Cc: "PHP-GTK Dev list" <php-gtk-dev@lists.php.net> Sent: Saturday, June 24, 2006 7:43 PM Subject: Re: [PHP-GTK-DEV] new GtkTreeModelFilter() vs. GtkTreeModel::filter_new()

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

-- PHP-GTK Development Mailing List (http://gtk.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php __________ NOD32 1.1380 (20060125) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com