Re: [Nautilus-list] Re: when that call to nautilus_directory_force_reload is not needed

[Yoann Vandoorselaere <yoann mandrakesoft com>]

Darin Adler <darin bentspoon com> writes:

> On Wednesday, June 13, 2001, at 12:44  AM, Yoann Vandoorselaere wrote:
> 
> > Darin Adler <darin bentspoon com> writes:
> >
> >> On Tuesday, June 12, 2001, at 04:09  PM, Yoann Vandoorselaere wrote:
> >>
> >>> AFAIK, the nautilus_directory_force_reload() in begin_localtion_change(
> >>> )
> >>> is bogus and should be fixed (*If* I remember right, I had a discution
> >>> with Darin a while ago about this, and, if I remember right, it is a
> >>> workaround for a problem (I don't remember which) :-) ).
> >>
> >> Basically the force_reload is not needed for local directories if FAM
> >> is present. So fixing the code to recognize that case and not force a
> >> reload would help performance a lot for a common case (if most
> >> distributions install FAM as well as Nautilus).
> >
> > I don't remember the exact reasons... Can you tell me ?
> 
> In our old code, before we added the reload, we got a lot of
> complaints from Nautilus users when they changed the location on an
> existing window to something that was invisibly cached by Nautilus, or
> opened a new window to something that was invisibly cached by
> Nautilus. 

Ok, I just had a look at the way Nautilus work when, for exemple, two
windows look at the same directory. If you create a file then reload
in one of the window, the other get updated. This is fine with me,
except that we are doing all operations two times (and as told in
a previous mail, this increase linearly each time a new window which
monitor this directory is openened).

Do you know of any solution that would allow us to do all the operation
one time, but share the result in all the windows ?



-- 
Yoann Vandoorselaere | C makes it easy to shoot yourself in the foot. C++ makes
MandrakeSoft         | it harder, but when you do, it blows away your whole
                     | leg. - Bjarne Stroustrup