Bug > 3.000 files in folder

Hello,

I found a bug in the latest stable version of FlashFXP (4.2.1.1745) and i use Windows 7 64 bits (so, on my PC, not in server (maybe, i don't know)).

When there are more than 3000 files in a directory and a file is added, the list does not update, you must leave the folder and come back.

Would you look?

thank you

By default FlashFXP will automatically refresh and resort the local list on update, however if the folder contains more than 3,000 items then the directory is only refreshed. The list is not re-sorted and the new items are added to the end of the list.

Are you 100% positive the local browser isn't showing the new items?

I know

200% ^^

There is no limit in the local browser so I am not sure why you are only seeing 3,000 files, have you tried refreshing the folder? Navigating out of the folder and back in should not be necessary.

I don't knwo but limit is 3000 (i have refreshed.. ^^)

Can you please send me a screenshot of FlashFXP reflecting the 3,000 limit.

Vidz (23secs) :

http://www.screenr.com/Bwh8

Thank you very much for the video. I am quite puzzled as to what might be causing it.

I watched your video and then attempted to reproduce the problem in the exact same way as you did using several different versions of FlashFXP.

My tests were conducted on Windows 7 64bit SP1 with a drive formatted with NTFS.

Unfortunately I was unable to reproduce the problem.

Actually, I think perhaps maybe the item counting is wrong off, After many attempts I am now seeing an oddity.

If I copy a single file into the current view the total and file count is increased by 2 instead of 1, if I then change to the parent and back the total is correct.

If I delete the file the count is decreased by 1.

I will continue to research this problem.

Please try this update and see if it resolves the problem for you
http://down1.opensightsoftware.com/FlashFXP42_1757_Setup.exe

This update resolves the issue that I noticed.

UPDATE: This update addresses actually two issues, the second issue relates to the way multiple refreshes are deferred, if a refresh was triggered during a refresh the refresh was thrown away, now its delayed a bit and then triggered. the delay equals the time it takes to complete the refresh request times a factor of 2.

No Fixed :/

Romainz has confirmed to me that this is now fixed in build 1758