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

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. In this case, the person would not see new files, nor would deleted files be missing.

This issue does not exist if you have FAM.

    -- Darin

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]