saturneric
File Panel in Windows version is not opening selected folder
Hi!
In the latest version, the File Panel in Windows does not open the selected folder in network drives. Whenever I select a folder in a network drive, the File Panel always displays system drives.
The frontend accessed network drives fine up to version 2.1.6 without any issues, but in this version, the functionality is somehow broken.
Thanks for your report!
I have tested two cases, both using Samba for access. Based on the test results, Samba seems to be working correctly, and no obvious issues were found. As shown in the screenshots, the network drive Z: (mapped to \192.168.16.1\media) is accessible, and both the cdrom and eric directories are correctly displayed in GpgFrontend as well as in the file explorer.
Could you provide more details about the specific issue you are encountering?
I apologize for not reporting it correctly.
I am using Windows on a MacBook through Parallels. Parallels accesses external drives connected to the Mac as mounted network drives, which are accessible and work fine. However, when I access local drives on Parallels using Windows Explorer, it displays them like local drives on Windows.
When I try to access the Mac local drive using the frontend in Windows, for example, to access the Documents Folder on the local drive, it displays the path as:
//Mac/Home/Documents/
And instead of showing the contents of this folder, it displays the mounted drives.
I didn't check the issue properly before reporting, and I apologize for that. It might be a low-priority issue. I'm not sure if this specific issue was present in previous versions or not. I'll check.
@marcos-morar No worries at all—every report is valuable, and I appreciate you bringing this to my attention. I'll make sure to look into it and try to reproduce the issue on my side. Testing may take some time, but I'll keep you updated on any findings. Thank you again for taking the time to report this!
Hi @saturneric
The UI of GpgFrontend has significantly changed since this issue was reported, and I believe this bug is now obsolete. Could you please review and close this issue if it's no longer relevant?
Thanks!