Bug
Each time a File Operation is performed in the qFlipper app (such as renaming, uploading, downloading, or deleting), the app forgets the currently selected file and defaults to the first item of the currently viewed folder. This makes multiple file operations harder from a UI perspective.
To Reproduce
Steps to reproduce the behavior:
Go to 'File manager'
Navigate to any folder
Perform any action on any file/folder
After completion, the view forces the first file to always get selected.
Expected behavior
The view should remember the index of the selected file after performing a File Operation inside 'File manager', and keep its place there.
If the action is uploading a file/folder, then the new index should be set to the newly added item.
If the action is renaming a file/folder, then the index should stay the same.
If the action is deleting a file/folder, then the succeeding file/folder should get selected. If no succeeding item exists, then the preceding item should get selected. If no preceding item exists, then nothing should be selected.
Actual behavior
The view forces the first file to always get selected after performing a File Operation inside 'File manager'.
Additional troubleshooting
Does the issue persist if you try multiple times?
Yes
Bug Each time a File Operation is performed in the qFlipper app (such as renaming, uploading, downloading, or deleting), the app forgets the currently selected file and defaults to the first item of the currently viewed folder. This makes multiple file operations harder from a UI perspective.
To Reproduce Steps to reproduce the behavior:
Expected behavior The view should remember the index of the selected file after performing a File Operation inside 'File manager', and keep its place there.
Actual behavior The view forces the first file to always get selected after performing a File Operation inside 'File manager'.
Additional troubleshooting
Logs LOGS.txt