[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: kio::netaccess and imagepreview
From:       Simon Hausmann <shaus () helios ! Med ! Uni-Magdeburg ! DE>
Date:       2000-06-13 9:23:57
[Download RAW message or body]



On Tue, 13 Jun 2000, David Faure wrote:

> On Tue, Jun 13, 2000 at 11:06:12AM +0200, Simon Hausmann wrote:
> > 
> > (cc'ing to mosfet because of the thumbnails)
> > 
> > On Sun, 11 Jun 2000, David Faure wrote:
> > 
> > > On Sun, Jun 11, 2000 at 10:38:45AM +0200, Simon Hausmann wrote:
> > > > The first one shows a nice loop of KIO::NetAccess::stat() being called
> > > > recursively from local event loops (this seems a good candidate for
> > > > Waldo's proposed reference counting?) .
> > > 
> > > Oooh. No, it's something different (the ref counting is in order to delay
> > > the kapp->quit(), which is not the problem here).
> > 
> > Hmmm, seems I misunderstood the refcounting idea. I guess a reference
> > counting which delays the kapp->quit() won't prevent the destruction of
> > the KTMainWindow. Hmmmm, so we need some way to catch all close
> > events? (installing an app-global event filter.. ouch ;-) no ;-)
> 
> I think I fixed this problem (of stat being called recursively
> for the image preview thing), when I disabled the "active icon under mouse"
> for thumbnails.

Ah, I see. But the user is still able to close the mainwindow during a
"single" KIO::NetAccess::stat() or download() call, no? (because we still
enter a "local" event loop)

And on slow systems like mine or when doing this over networks this
happens quite easily.

Actually I guess every app using KIO::NetAccess and not doing a
are-we-doing-a-net-access-operation check in MyKTMainWindow::queryClose is
affected?

> > > > BTW, shall we really name the thumbnail directory .mospics? I mean, it's
> > > > probably cool for mosfet :-)) but it doesn't tell very much. How about
> > > > calling it .kthumbs or so? Just my HO :-)
> > > I agree. Now try to convince him :-) 
> > 
> > Mosfet? :-)
> 
> ;-)
> And then he'll talk about compatibility with what the users already created :/

In my HO this is no problem, as we never said HEAD is meant to be
compatible (at least on this level ;-) , until it is finally released.

What's your opinion?


Bye,
 Simon

[prev in list] [next in list] [prev in thread] [next in thread]