-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long file paths are not properly displayed #73
Comments
I don't know if you're already aware of this, but you can swipe horizontally on the folder path. If you swipe completely to the right, you should be able to tap on the "internal" / "SD card" button without any issues: In general, I agree that it would be easier if the overlapping part would move behind the "internal" / "SD card" button. |
I was indeed aware, but thank you for specifying it anyway. So it is true that the bug is above all graphic. Besides, it makes me think that I forgot a detail, namely that the bug appeared in Simple File Manager v6.16.1, it was not present in v6.16.0. At the time I reported the problem I had looked at all the changes between these 2 versions in the GitHub history. As I am not a programmer, I could not deduce anything from it, but maybe someone more experienced could do it. |
It should wrap, ideally. File paths can become long enough on AOSP's EXT4 FS that that would be necessary. Otherwise, at least add a scrollbar, and/or make it editable upon request as https://apps.kde.org/en-gb/dolphin/ does. |
Hi !
I first reported this bug in the Simple File Manager repo #758 but I prefer to republish it in general issues as I know the problem already affects Fossify Gallery.
When browsing the file explorer, a long file path can be superimposed on the "internal" or "SD card" button, making it difficult to click. This also happens when you select a destination to copy or move file (e.g. in the gallery when you are moving a photo).
I can't support you financially for now so I hope this will help you a little. Thank you for your work ;)
The text was updated successfully, but these errors were encountered: