Hi,

Around christmas I added grouped downloads to gtk2.  This is what I know
about the grouped dl's stuff, if you're not talking about that or if
this part of the code has changed drastically since then, I apologize (I
haven't been coding on gtkg much at all since then).

I think that when I left it "abort" didn't work if you had a grouped
download chosen but all the "abort by..." options worked with multiple
files selected, grouped downloads or single source downloads.

However, the way gtkg used to handle downloads (it may have changed by
now, apologies if so) was that when you'd choose a file to download it
would go into the 'fileinfo' tab.  Even if you "aborted" all the
"sources" (which appear in the download tab not the fileinfo tab) gtk
would keep looking for more sources.  You had to actually go to the
fileinfo tab and "purge" the download. This behaviour was the topic of
some discussion and ideas were brought up.  I don't think we ever
changed it though, but we should.  When a user 'aborts' a download, they
don't expect it to start again with different sources.  Not to mention
that you can only purge one fileinfo at a time.

I think this is the behaviour in gtk1 too though... and it is structual,
ie. we need to figure out what the heck we mean by downloads, sources,
fileinfo, etc. and change how gtk is managing them.  As opposed to it
being a bug in the "abort" code (though I'm sure there are those too).

Emile

ps. I changed my last name from "le vivre" to "roberts" for those
wondering who I am.


On Tue, 2004-05-25 at 00:32, clayton rollins wrote:
> On May 25, 2004, Christian Biere <[EMAIL PROTECTED]> wrote:
> >
> >Hi,
> >
> >I don't use GTKG often as an "user" (believe it or not) and I had used
> >the GTK+ 1.2 interface lately. Anyway, currently I'm using the GTK+ 2.x
> >interface to do a little debugging. It turned out that "Abort all by
> >..." doesn't really work and sometimes the CPU usage is really high for
> >a few seconds after I had clicked on it.
> >
> >At first, I thought this was caused by my recent changes but I couldn't
> >find anything which would cause this. I've checked out the -current
> >sources from a week ago and notice the same problems. Just to be on the
> >safe side, could someone confirm that these problems exist longer than
> >a few days?
> >
> 
> I can confirm with a copy of the HEAD branch cvs'ed on april 11.
> 
> Here, it aborts all the current download entries, but leaves the download
> active and collects new sources.
> 
> CPU usage doesn't seem too eratic, but does raise a bit when aborting.
> (dual amd 1300 Mhz, though, and SMP would likely help here,)
> 
> Regards,
> Clayton
> 
> _________________________________________________________________
> Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! 
> http://join.msn.click-url.com/go/onm00200362ave/direct/01/
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g. 
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Gtk-gnutella-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
> 



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Gtk-gnutella-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel

Reply via email to