Quoting Emile le Vivre <[EMAIL PROTECTED]> from ml.softs.gtk-gnutella.devel:
:So the patch as submitted yesterday should make the passive search
:sorting behave correctly as far as I can tell (please let me know if
:it's otherwise).  I can quite easily create a patch that removes the
:count record value altogether and uses a gui lookup for column sorting
:for all sort by # cases.  Functionally it'll be worse but it'll be
:neater in code.  Let me know.

I would prefer a patch that would use a '#' stored somewhere else than
in the record, with clear commenting about why it is done that way.

Can you explain why performance is lower when '#' is stored in the GUI
instead of in the record?  Does the problem exist in GTK1 only, or does
it apply for GTK2 (I would assume the latter).

I don't really mind if it's slower because the current behaviour is
not correct.  You can make any program fast when you sacrifice correctness!

Raphael


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Gtk-gnutella-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel

Reply via email to