Open boypt opened 5 years ago
The file browser in the UI listed all the files on start and pushed the whole to the client to display which is inappropriate.
Plus it has a limitation of 1000 files in total. If you have more than 1000 files in the download folder, some of them will be omitted and the display is corrupt. If you remove this limitation, all files are displayed correctly but very slowly if the number is too big due to the first problem.
The file browser in the UI listed all the files on start and pushed the whole to the client to display which is inappropriate.
Plus it has a limitation of 1000 files in total. If you have more than 1000 files in the download folder, some of them will be omitted and the display is corrupt. If you remove this limitation, all files are displayed correctly but very slowly if the number is too big due to the first problem.
yes, this is a problem of the original design. It's better to keep the download folder clean after download.
@boypt Do you have any plan rewriting this part?
@snowie2000 no, not at the moment, I'm not sure what to change. The original idea is that with the help of velox library, automaticly transfer differentces of the filesystem, and display the whole directory tree in web. Too much files reusult in chaos in the UI thus adds a limitation of 1000 files max.
Removing the mechanism also removes the realtime update feature, and that needs another UI interative designing, I think that's too much work.
Files listed in[ since 1.0.16 user can collapse the section and expand again to refresh display] [fixed v1.2.5]Download
may be duplicated during task initating.changes to config in web UI may not success, if config.json can't be written.[ since 1.0.16 a write error will show up on web UI]Windows: program may keep flushing errors about
wsarecvfrom
as mentioned at #16 , this is a upstream problem while program still works. SetMuteEngineLog
option to hide such logs.