The following fixes/changes since v6.1
110+ Changes
-- Build 2144 RC ( 2016-05-05 )
FIXED - Search Dialog will disable it self during search
FIXED - Content search will stop searching faster if stop command is issued
FIXED - Issue with binary content search that hanged searched in some situations.
FIXED - Call Unpack from script will now only unpack browsable files.
ADDED - CustomCommand "MC.CloseAllTabs" have a new option paramter "DONOTASK", This will prevent confirm dialog for locked tabs.
FIXED - 1 rare stability issue
-- Build 2140 ( 2016-04-30 )
CHANGE- Pack/Unpack now also use the new way to initialize file operations
FIXED - Unpacking password protected 7Zip from script now works better
ADDED - Unpacking Zip file with wrong password will now ask again for password
FIXED - Fixed issue with search and content search
FIXED - 2 Rare stability issues.
FIXED - Many internal changes.
-- Build 2135 ( 2016-04-23 )
CHANGE- Major rewrite how Copy/Move file operation are initialized (From copy/move button is pressed until copy/move is started)
ADDED - Temporary tweak setting in core setting, that will enable the old code path for starting copy/move (just in case)
ADDED - MultiScript functions for using the Advanced Filter engine from script.
(FilterCreate, FilterLoad, FilterLoadById, FilterSave, FilterAddRule, FilterIsMatch)
ADDED - ShellContext menu 'new' updated to work with the new way program can register for this. (Like newer MS Office do)
CHANGE- Drag on Drop to same location will show the drop popup menu
FIXED - Holding ctrl and starting a drag/drop operation now works better.
FIXED - FindFiles content search could crash in very rare situations.
FIXED - Defining an empty array in MultiScript was not empty. Has 1 item, (that was unassigned)
Major rewrite of Initialize of Copy/Move Operation
This release contains a major rewrite of how copy/move operation are initiated and queued.
For example everything from when you press F5/F2 to start copy, until the file operation is actually queued. Like how the dialog works and how it finds settings and and how it queues file operations and lots of other minor boring details are changed.
It is not something that you will notice, since it is still the same UI (dialog) But under the hood everything is changed.
and hopefully I have not broken anything.
BUT if I have.. There is a temporary settings in Core Settings that will enable the old code path instead.
You find it under the "Tweaking" section in the FileSystem Tab. But hopefully you will not need that.
Filters and MultiScript
The advanced Filters can now be used by MultiScript
For example this script till get all item items from the source panel.
and it then creates a filter that will match the Fullname and using 'Contains' matching with "Frog"
When done it will then set all the matching items as selected.
You can add many rules to a filter just like in the Advanced Filter setup.
You can also Load existing filters by ID or save/load to/from file.
@var $matches[];
@var $items = GetSourceItems(1);
@var $hFilter = FilterCreate();
FilterAddRule( $hFilter , "Fullname" , "Contains" , "Frog" );
@var $cnt = arrayCount($items)
for( $i = 0; $i < $cnt; $i++)
{
$item = $items[$i];
if(FilterIsMatch($hFilter, $item))
{
$item = PathGetNamePart($item);
arrayAdd($matches , $item);
}
}
SetSourceSelected($matches, 1);
Filter Script function are.
<handle> FilterCreate();
<num> FilterAddRule( <handle> , <Field to match> , <Match Type>, <Value> , [ Optional, set to 1 to invert rule)
<handle> FilterLoad( <filename> );
<handle> FilterLoadById( <guid of advacned id> );
<num> FilterSave( <filename> );
<num> FilterIsMatch( <handle> , <full path to file> ); // return 1 for a match, 0 for not a match
The Field / Match type for FilterAddRule are the names you see in the Advacned Filter dialog.. I will input the exact one here later
