Bug: Integration with Listary Broken After Update to v4.0.0 — Path Information Not Provided #17550
Description
Description
After updating the FILES application to version 4.0.0, its integration with the efficiency tool Listary has broken, preventing the correct transmission of path information.
Listary Commands Failure: Previously, it was possible to set up commands in Listary's "Commands" feature window that utilized the {current_folder} variable to obtain the current directory path from FILES. This feature is now broken; the variable no longer retrieves the correct path.
Core Dialog Switching Failure: Listary's most critical feature — the ability to quickly switch any system File Open/Save dialog to the path currently being browsed in FILES — has also completely failed. This severely disrupts workflows reliant on the combination of FILES and Listary.
Steps To Reproduce
- Ensure Listary is installed and FILES is at version 4.0.0.
- Test Function 1 (Commands):
- Open any directory in FILES.
- Summon Listary and enter a pre-configured command (e.g., one that launches a terminal, incorporating the {current_folder} variable).
- Result: The command executes but does not start in the intended target directory.
command such as:
SVN update current directory
directory: tortoiseproc.exe
param: /command:add /path:"{current_folder}"
work directory: "{current_folder}"
- Test Function 2 (Dialog Switching):
- Open any directory (Directory A) in FILES.
- Open a "File Save" dialog in any application (e.g., VS Code).
- Summon Listary and attempt to use its feature (e.g., by typing the path or using a hotkey) to switch the dialog's current directory to Directory A (the one browsed in FILES).
- Result: The switch fails; the dialog path remains unchanged or an error occurs.
Files Version
4.0.0.0
Windows Version
10.0.19045.6093
User ID
32ef2c08-7c4d-49d1-bdaf-ab4af9c33c4c
Log File
Open Log Location this function failed either😂