91
Support and Feedback / Re: Quick filter
« Last post by total_annihilation00 on May 09, 2026, 20:40:41 »Ctrl+F for the Filter Box focus then Backspace to erase & Escape to return to the main view.
MultiCommander v15.8 is released!
@var $listfile = TranslateEnvString( "%TEMP%" ) + "\\tc_list.txt";
@var $paths = GetSourceSelectedPaths();
@var $target = GetTargetPath();
SaveArray( $listfile, $paths, 1, 1 );
@var $args = "Copy *\"" + $listfile + "\" \"" + $target + "\"";
MC.Run CMD="C:\Program Files\TeraCopy\TeraCopy.exe" ARG="{$args}"
As I said above.. Single file zip was the issue. There is an optimization for zip with only a single item in them, and it did not create the target path if it was missing.I can extract a zip with subfolders and they are created. Can you explain what you are doing.. What do I have to do to reproduce it ?Simply select the ZIP file without opening it and extract it with Alt+F6. Then the main directory with the name of the ZIP file should be created in the target directory, and this should also work for multiple ZIP files at the same time, if I’m not mistaken. In any case, the main directory named exactly like the ZIP file is not created, and the error message appears instead. Edit: "Unpack Archives into individual Folders" have to be enabled.
I can extract a zip with subfolders and they are created. Can you explain what you are doing.. What do I have to do to reproduce it ?Simply select the ZIP file without opening it and extract it with Alt+F6. Then the main directory with the name of the ZIP file should be created in the target directory, and this should also work for multiple ZIP files at the same time, if I’m not mistaken. In any case, the main directory named exactly like the ZIP file is not created, and the error message appears instead. Edit: "Unpack Archives into individual Folders" have to be enabled.
The error described above bothers me too. I have also noticed that when extracting with Alt+F6, directories are no longer created automatically, and instead an error message appears saying that the target path does not exist.
Well As written in changelog. entire fileoperation engine is redone so errors in that is expected..
But I can't reproduce this. I can extract a zip with subfolders and they are created. Can you explain what you are doing.. What do I have to do to reproduce it ?
The error described above bothers me too. I have also noticed that when extracting with Alt+F6, directories are no longer created automatically, and instead an error message appears saying that the target path does not exist.
The settings for new tab works.. t must be that custom column layout overrides it and cause it to reset it.
because that happens after. And I think it does not work because of another bug that was fixed. so it worked because something else was broken.


MC.Explorer.Sort COLNAME="Date" ORDER=DES
That settings are the default column and order for new tabs that are created.
If I set Date/Time and Ascending.. Press Apply.. and then create a new Explorer Panel tab.. The sorting is set to date with ascending order..
I've configured MultiCommander (V16 3157 Beta) to use "Date/Time Descending" as the default sorting order. Historically, this setting persisted correctly across sessions. However, after the latest update, the sorting reverts to "Name Ascending" upon opening new tabs, despite being set to "Date/Time Descending" in preferences.
Additional issues include:
- When applying a stored layout ("My Advanced Tweaks") via 'Use Column Layout', the sorting resets to "Name Ascending" in the main view.
- Creating a new layout with "AutoLoad On Paths" (specifically setting paths like C:\, D:\, G:\, etc., and enabling "Valid for Future Paths") via the dialog causes the sorting setting to break—reverting to "Name Ascending" on new tabs.
- This issue appears linked to the handling of "AutoLoad On Path" entries when creating or modifying layouts.
- Despite selecting the desired Sorted Column ("Date/Time Descending") and enabling "Remember Sorting" in the Explorer Panel, the sorting reverts to "Name Ascending" upon restarting MultiCommander (V16 3157 Beta). The setting should persist across sessions, but it appears the Sorted Column configuration is not retained on re-launch.
- This issue seems to be more than just "AutoLoad On Paths"—the latest beta does not correctly apply or restore the Sorted Column setting during startup, indicating a regression in the persistence logic for sorting preferences.
I verified that the issue is not present in older versions (e.g., V14.4 3047), where the sorting and layout behaviors work as expected. It seems the bug is related to how "AutoLoad On Path" interacts with layout persistence and sorting settings in the latest build.
Please investigate and fix this regression, especially ensuring that:
- Sorting preferences are persisted across sessions and tabs.
- "AutoLoad On Path" settings in layouts do not interfere with sorting state.
Thanks.