Re: Threading woes

On 12/31/2004 03:53:27 AM, Andrew Conkling wrote:
Well, now that I've settled into using Balsa (and themed the icons!), I've noticed that the threading is often counterintuitive or counterproductive. For example: The status of threads is preserved through the session, but is not saved on exit.

Saving the expanded/collapsed state of all threads in all mailboxes could really slow down both exit and restart. Balsa could perhaps save the current message and expand to it on reopening--would that help?

When a new message is put in an existing (open) thread, that thread is closed.

Should be fixed in cvs.

Opening a multi-level thread means opening each message; it seems more useful to have the entire thread open when the first message is expanded.

That's the natural behavior of GtkTreeView--changing it might make Balsa less consistent with other Gtk apps. You can use the GtkTreeView key bindings shift-numberpad-'+' or shift-cursor-right to expand the whole thread.

And, of course, there's that hard-to-squash bug with the last thread in a list....

Reported as a GtkTreeView bug:

Is there any way to fix any of these,


or are they just shortcomings in GTK?




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]