Hi,
Some of those have already been flagged on Github, but here are my 2 cents :
System tray, background mode, launch at startup…
Those issues seem crucial to me. IMO, considering the software purpose, it should not appear in taskbar/dock and be managed via system tray.
- If possible consistently across platforms, the best behaviour would be to appear in taskbar/dock only when the main window is visible (then allowing the user to focus it via ALT/CMD-Tab), and disappearing when the window is closed. I’ve seen it on Windows, but I’m not sure if that’s possible on macOS though (can’t find an app that I use that does it).
- Left click on the systray icon should open/close the main window, and right click be implemented with the current menu items “Open” and “Quit”. Additional items could be added, like “Unmount all vaults”.
- Currently, closing the main window when no vault is mounted causes the app to instantly quit. IMO correct behaviour should be minimize main window and go to systray.
Global settings
As pointed out by users, options to launch at startup, launch in background… should be available directly in-app instead of forcing the users to interact with OS-level configuration.
Per-vault settings
I’m on macOS using Path Finder as a Finder replacement, and for a reason I can’t explain the folders are opened using Finder instead of Path Finder even if the command issued by your MacMounter class is “open” which when used in Terminal opens Path Finder correctly.
I’m aware that this point is not relevent to most users but I think an elegant way to handle this and many other advanced usages would be to replace the “Reveal Drive” checkbox by a select field “On mount” with options “Reveal folder” (default), “Do nothing”, “Execute a command”.
Selecting the last option would reveal a text field allowing the user to input a command that would be executed after replacing a specific placeholder by the directory path. An informative label should be present under the field to inform the user of the placeholder to use (e.g. $DIRECTORY).
That would solve my specific issue (running “open -a ‘Path Finder.app’ $DIRECTORY” would do the trick), but would also allow users to easily run any custom scripts and hooks directly from GUI.
For good mesure:
- If complex syntax (chaining commands with “&&”…) is supported by the underlying code, placeholder replacement should handle multiple occurrences.
- If this point can be implemented, it would be trivial and probably useful in some cases to have a similar “On unmount” field with options “Do noting” (default) and “Execute a command”.