aMule Forum
English => en_Bugs => Topic started by: morph on November 26, 2005, 03:21:25 PM
-
Hi,
I'm reporting some bugs in search facility of amulegui
- a local server search never stops, or better, the button "stop" stays on and "start" stays off even if the search is finisched
- selecting the "extended parameters" and choose some of them, seems they were not used: I've select "archive" as type, but even audio files come out
- the previous point is different: the extended parameters of the first search are used for all the other searches: if you choose no ext'd params at the first search, then even changing them for the following ones, the original params will be used. If you modify those params BEFORE the first search, then they last even for the news searches.
Bye
-
one more:
during global search, no progress bar is displayed.
Regards.
-
Mentioned bug must be fixed today.
during global search, no progress bar is displayed.
Known. Not implemented yet.
-
Great!
Just a question: don't you think should be better that amulegui and amule would share the gui code? I mean, amulegui should be an amule without the core to manage files, slots, connections, etc, but the gui should be the same.
I don't know how the project is structured, and neither if it's possible to use just one "code library" from the gui part of amulegui and amule, otherwise it seems to me that some code is written twice, one for amule (that seems ahead in development) and amulegui.
Thanks & Regards.
-
They do share the same code, however the information has to be transfered from core to gui, and that needs to be added manually mostly.
-
oookay, understood.
Maybe you could think about import amule.conf keys (where needed) into remote.conf: i don't want to configure both twice, but i'd like at least, modification in amule will be available in amulegui as well.
So i can tell you that the sources are not passed from core to amulegui (yet, i suppose).
Thanks & Regards.