| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
| |
accidentally get passed through to the loading mechanisms (usually after a drop event or other file operations).
|
| |
|
|
|
| |
1) When copying/cutting files, also place a copy of the file list into the standard text/uri-list mimetype (with the local file URL syntax: file://) - This allows the files to be seen by other applications (if supported)
2) Also update the drag/drop functionality to use the standard text/uri-list format for all drag/drop operations. This allows movement of files between apps (such as moving a local file into a web-based file paste site).
|
| |
|
|
| |
clean up the "cancelling" of a file operation.
|
| |
|
|
| |
might be getting shown to the user. Use this dialog for checksums as well.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Seemlessly embed the ZFS rollback options into the main dir browser (simple time slider at the top).
2) Take all the main widgets and put them into separate classes/files (widgets/*)
3) Add support for both tabs and columns for multiple directory viewing
4) Remove the "icon" view mode, and replace it with an icon sizing option (larger/smaller)
5) Add the ability for the multimedia player and slideshow viewer to be running within separate tabs while still browsing the system (new files will be added to the queue instead of replacing it)
6) Ensure that only selected files are added to the player/slideshow on demand.
7) Add the ability to zoom in/out on a slideshow image.
KNOWN ISSUES:
1) The new file/dir functionality has not been replaced/re-implemented yet.
2) The drag and drop functionality has been removed until a new implementation is put in.
PLEASE TEST:
ZFS snapshot use, multimedia file player, browsing and other UI changes
|
| |
|
|
| |
that way we can't run into the situation where the dir is removed because of the conflicting destination.
|
| |
|
|
|
|
| |
1) Fix the double-run of the background dir checker when changing directories.
2) Add the file overwrite checks to the cut procedures in the backend.
3) If a file/dir is copied onto itself, just skip it rather than erroring.
|
| | |
|
| |
|
|
|
| |
1) Move all the File operations into a seperate thread (GUI no longer lags when performing long operations).
2) Streamline/simplify the time spent looking for snapshots of a directory (re-use the base snapshot directory found if it is still the same directory - no need to search for it again).
|
| |
|
|
|
|
|
| |
1) When finding a file mimetype, try a case-insensitive filter if nothing came out of the case-sensitive search.
2) lumina-fm: when removing a slideshow file, try to automatically go to the next/previous picture instead of index=0;
3) Add a bunch more processEvents() calls to the lumina-fm file operations dialog. This should keep the UI's more responsive and update the visuals more often while running operations on large numbers of files.
4) lumina-fm: Fix another upper->lower case extension issue when checking if a file is supported by Qt's read/write operations.
|
| |
|
|
| |
well. This means that copy/past/remove will properly perform on every file/dir within the target directory.
|
| |
|
|
|
|
|
|
|
| |
Also do a large clean up of the file operations in lumina-fm:
1) When doing copies of directories, make sure to properly copy all child files/dirs (no matter how deep)
2) Clean the order of directory copies so that you can successfull make a copy of a directory into itself (copy ~/Test -> ~/Test/Test for example)
3) Check for attempting to *move* a directory into itself and show a warning to the user about an invalid operation.
4) Get the total number of files/dirs to be operated on before starting operations. This allows the UI to be more detailed about what it is doing at that particular time.
5) If a directory fails to copy for some reason, don't try to copy all the children of that directory either (they will all fail and just bloat the list of errors)
|
| |
|
