Multi Commander > Beta Releases

v11.0 - Release Candidate (Updated 18-Feb)

(1/7) > >>

Mathias (Author):
Current UserDefinedCommand will be auto converted to a new format.
The old UDC file was UserDefinedCommands.xml and it will be rename to UserDefinedCommands.xml.bak-Migrated
So if you revert back to old version. You need to rename that file to get back your commands

The new version store UDC Scripts in Config/Scripts/ Script can be seperate *.udc file or bundled together as a zip.
They can also be organized in folders. Script/Examples/ contains examples script.
If modifed then do not keep them inside the zip. since this zip will be update on new versions.

** 26-Jan **
In build 2756  there is a change in what icons sizes is used. Before there was 4 icons sizes  16,24,32,48 . This is still true.
So when scaling to 125% it picked the icon closest in size and used that. for 125% it was 24px. but 24px is actually a 150% scaling of the 16px, it should have been 20px.  But because of reasons there was no support for scaling the icons during drawing. But that has now been fixed. So if you run at high scaling you MIGHT see the icons have shrunk in size. This is because now their are drawn in the correct size. If you want then bigger change the icon size settings in Core and Explorer Panel settings. Small, Medium , Large, xLarge can be selected. and the icon will then be scaled depending on Windows Scaling settings-

As you can see in this table. You see the actually icon size depending on scaling and icon size selected
         100%  125%  150%  175%  200%  225% 250%
Small     16    20    24    28    32    36   40
Medium    24    30    36    42    48    54   60
Large     32    40    48    56    64    72   80
X-Large   48    60    72    84    96   108  120


Release v11.0
-- 2768 - 18-Feb-2021
   FIXED - Backup/Restore now also include the new Script files
   FIXED - MultiUpdate update log is now more detailed
   FIXED - MultiUpdate will show crashreport dialog if crashed
   ADDED - MC.Explorer.Goto support ItemFocus= parameter to set focus after scan
   ADDED - Will show a message at startup if there are problem loading extension/modules (Failed to be upgraded?)

-- 2765  - 13-Feb-2021
   FIXED - Various DPI Scaling issue in FolderTree, CheckSum extension, MultiRename
   FIXED - FindFiles dialog now closes on Escape key again.
   FIXED - WindowsExplorer styled setup will now map F3 to search again.
   FIXED - 1 Stability Issues
-- 2761 - 5-Feb-2021
   ADDED - :SysInfo command now includes Monitor information and Windows 10 Release ID
   ADDED - MultiTags  ${pid}, ${mctemp} , ${sourcefocusext}, ${targetfocusext}
   ADDED - Example script with all multitags
   FIXED - UserDefinedCommand Dialog fixes
   FIXED - Scaling issue with the width of items shown on statusbar
   FIXED - Toolbar still visible if all toolbars disabled in config

-- Build 2759 - 30-Jan-2021
   ADDED - Drag and drop of script in UserDefinedCommands-Dialog to move to subfolder
   ADDED - Heigh of Freespace field is now calculated better
   FIXED - 1 Stability Issues

- Build 2756 - 26-Jan-2021

   ADDED - MultiScript with external ref can now be views or converted from MutliScript editor.
   ADDED - Added more Examples script
   FIXED - *.UDC script files with multilist comment/desc can now be loaded
   FIXED - Fixed issue with wrong icons sizes used in 125% / 175% scaling, Will now be drawn in correct sizes and scaled if needed
   FIXED - Copy 1 folder, and it is empty. Datetime is now kept is option for that is enabled.
   FIXED - Portable mode overwrite as a empty xml
   FIXED - 1 Stability Issues and many icon scaling issues at 125%/175% scaling

 - Build 2751 - 7-Jan-2021

   ADDED - MultiCommander.exe CommandLine command /OPEN now support more paramters  /PANEL=Left|Right|Active|Source|Target and /NONEWTAB is added
   ADDED - MultiCommander.exe CommandLine command /QUIT to exit current running instance
   FIXED - CommandLine field will now try to do auto complete on paths when starting to type.
   FIXED - MultiDataViewer - HyperLink in text that was formatted was not always clickable
   FIXED - MultiDataViewer - Text Formatting that formated text to end on line. did not block formatting that was inside.
   FIXED - MultiDataViewer - Text with multiple formatting sometimes lost formatting when parts was selected
   FIXED - MultiDataViewer - Sometimes crashed if selection was done over part with multiple formats
   ADDED - Minor Redisgned to UserDefinedCommands dialog (TreeView and Icons and DarkMode Support)
   ADDED - Example script is included in release
   ADDED - Old UserDefinedCommand scripts will be migrated to scripts/*.udc script files
   ADDED - UserDefinedCommands can now be loaded from zip
   ADDED - UserDefinedCommands file format changed.
   FIXED - Tweaked detection if file is binary during content search and file viewer
   FIXED - Minor tweak and code cleanup
   FIXED - 3 Stability Issues

Hi Mathias.

Yesterday I updated my test environment (portable 64-bit) to 10.3 and there was an issue:  The file was created as a 49 byte (broken) xml file containing only

--- Code: ---<?xml version="1.0" encoding="UTF-8"?>

--- End code ---


I would like to know your thinking behind the (big) change to scripts.  For example, it is now impossible to edit MultiScripts within MC?

Mathias (Author):
eh that is should not be xml.
the example file is a zip with couple of script included . so not sure how it can be 49 bytes and xml..
the current script will be converted into seperate files in the script folder.. they will still be possible to edit them. From inside MC there should be no differnce.
only the way they are saved to disk are changed.


--- Quote from: Mathias (Author) on January 10, 2021, 01:34:24 ---eh that is should not be xml.

--- End quote ---

Yes, I was surprised!  I was able to extract from the portable installer.

OK - I see why I thought that MultiScripts could not be edited:  The .UDC files store only a reference to the (external) files my scripts are exported to.

Still can't see why the storage method was changed.  The rest of the app uses .xml config storage...

Mathias (Author):
It was a bad format. you could not edit script in another editor. it was harder to share script since by default they was all saved in the same xml.
You can now also buddle you script up in a zip. And you are able to have them organized in folders. So admin can for example push out common script for users. without touching personal script files.


[0] Message Index

[#] Next page

Go to full version