I have to agree. I'm using aMule CVS 0429 in Windows. On a LAN, the GUI works fine. Over the internet, it fails when downloading transfers (never see anything). I presume it's something to do with the update interval. Other things like shared files, settings etc seem to work. "Amulecmd -show dl" works as well. Even if the auto adjusting update interval works better, IMHO a manually specified update interval option would still be good. Preferably in the GUI not in the main program (or both). Sometimes you don't really want realtime monitoring of what aMule is doing, you just want it there so you can check it occasionally so even an interval of like 2 minutes or more may be fine. And if you forget to close it or whatever, you don't want it clogging the connection for no good reason. Yes you can (mostly?) do this with the web interface and the command line client but for a lot of people the GUI is probably a lot easier to use especially for things like pausing or resuming many files, sorting files into categories etc (for the GUI, even seeing what's being downloaded or what's completed if you have a lot of files). But if it's on your LAN or on the computer you are using now, there's probably no real harm with more or less real time monitoring, indeed you probably want to use it like you will use aMule monolithic.
Of course, perhaps it will end up being better to split the gui yet again into a local and remote gui, but I hope not.
