| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
Also so the same for the "properties" option (although it only operates on *.desktop files at the moment).
|
| |
|
| |
|
| |
|
|
|
|
| |
because it operates on Files/dirs, not URLS.
|
|
|
|
| |
of XLib. This bahaves exactly the same on my FreeBSD 10.x system - still need to test a FreeBSD 11.x system.
|
|
|
|
|
|
| |
1) Make sure the background routine *only* runs if the directory has changed or been modified (changing the view/config will no longer re-scan the dir)
2) Cleanup the number of translated strings in the dir info routine, and make it easily modified for larger file sizes (already increased to TB now).
3) Ensure that the whole-dir info is re-displayed if the selection is cleared.
|
|\ |
|
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
(Contributed by william-os4y)
|
| | |
|
| |
| |
| |
| | |
Refactoring of the procedure
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
currently-active favorite with the same name. If the current favorite is stale/broken - go ahead and replace it with the new one.
|
| |
| |
| |
| | |
the system time (whatever that might be).
|
| | |
|
| | |
|
| |
| |
| |
| | |
Userbutton icon.
|
| | |
|
| |
| |
| |
| | |
it will always start with the canonical path (no sym links or redundant paths).
|
| |
| |
| |
| | |
ther is crashing on occasion - still not sure what yet.
|
|/ |
|
|
|
|
| |
still appears to be able to "drop" items outside the window (for other applications) and has strange behavior in those cases (although non-critical - it does not change the filesystem in any way).
|
| |
|
|\
| |
| | |
add "New file" on lumina-fm
|
| | |
|
|/
|
|
| |
NOTE: This option does not retroactively remove thumbnails that have already been loaded - it only prevents loading thumbnails in new directories.
|
| |
|
|
|
|
|
| |
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).
|
|
|
|
| |
the current item when re-loading the files in the directory (caused issues when remvoing files from within the slideshow viewer).
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
1) Add the ability to remove the current file loaded into the slideshow
2) Add the ability to rotate the current slideshow image by 90 degrees (clockwise or counterclockwise) and will re-save the file itself.
|
| |
|
| |
|
|
|
|
|
| |
Conflicts:
debian/changelog
|
|
|
|
| |
allows a user to run qmake LIBPREFIX="something" PREFIX="something" to ensure that libraries are found in the proper location.
|
|
|
|
| |
LuminaSingleApplication usage (which auto-loads translation files).
|
|
|
|
| |
apply the relative path fixes to all LSingleApplication's forwarded inputs.
|
|
|
|
| |
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)
|
|\ |
|
| | |
|