[Mldonkey-bugs] [Bug #2834] 100% is not 100%

[nobody]

=================== BUG #2834: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2834&group_id=1409

Changes by: Anonymous user        Date: Tue 03/18/03 at 11:42

------------------ Additional Follow-up Comments ----------------------------
Something must be missing to notify the GUI of the file state change 
(Reconnecting to the core fixes the display bug).



=================== BUG #2834: FULL BUG SNAPSHOT ===================


Submitted by: hallibaby2              Project: mldonkey, a free e-Donkey client
Submitted on: Sat 03/15/03 at 20:28
Category:  Core                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  None                        Release:  2.04 above                  
Platform Version:  None               Binaries Origin:  Compiled From CVS   

Summary:  100% is not 100%

Original Submission:  Think of a file which is downloaded 100$ (even verify 
chunks) and moved to incoming directory. Now think this file is still in 
download but in incoming directory. Now think (as I did) you cancelled 
downloading this file because it is in the incoming directory. And now look 
inside the incoming directory....the file which was existing inside the 
incoming directory before cancelling download is now disappered.


What's wrong?

The file was there (incoming and 100% - I have checked this) although being in 
downloading list?!?!? And now.... it's lost!

Greetz
Stephan Haller

Follow-up Comments
*******************

-------------------------------------------------------
Date: Tue 03/18/03 at 11:42         By: None
Something must be missing to notify the GUI of the file state change 
(Reconnecting to the core fixes the display bug).


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2834&group_id=1409