ok, i did some additional testing and now i can't reproduce this effect anymore. very weird, it appeared reliably yesterday after multiple restarts and tinkering with various config parameters.
anyway, i guess that's good news... sorta. i'll keep an eye on it...
kry, i found the cause of the server connection problems that i had yesterday after a restart of amule: when you start amule and it loads the servers from the server.met, the order of the digits of the ip-addresses are flipped (1.2.3.4 becomes 4.3.2.1), so amule tries to connect to the wrong ip's. i remember old versions of the offical client having the same problem on the mac.
the easiest workaround is to clear all servers from the list and then to get a fresh server.met.
i really have to say, i'm already pretty contend with the current version -- a little more polishing here and there and we can start getting joe average mac to switch to amule...

EDIT:
two vanishing issues:
- first one is a server issue: amule removes even valid servers from the server list until no servers are left. whenever you get a handful of new servers from another client they get added to the list but vanish soon, too.
- second one concerns the display of clients that are downloading from us. i took a screenshot that illustrates the problem: in this particular case the first two list entries are filled with the window background so that you can't read the information that's supposed to be there. if you sort by different columns you can alternate which particular client is displayed in the remaining row.
after i took the screenshot the problem went away, but now it's back there again. my guess is that it vanishes when there are no filled upload slots to display, but in order to confirm this i need to do a bit more testing.
[/list]
