How to migrate macros and scripts from version to version 2022.2.0.34?

How to migrate macros and scripts from version to version 2022.2.0.34?


    Jan 21, 2023#1

    I have a computer running UltraEdit version on Windows 10. I have a second computer running Windows 10 on which I have just installed the trial version of 2022.2.0.34. (I can't purchase the 2022.2.0.34 license, but that is another issue that I've already reported to UltraEdit support via email.) I want to use the macros and scripts from the old version on the newer version on my second computer.

    On the older version, I did an Export Settings. It exported 133 files (.ini, .in0, .uek, .mb1, .pb1, .tb1, etc.). When attempt to import the settings on the newer version, it's looking for a .uec file. There is no .uec file. Please advice. Thanks. 

    Grand MasterGrand Master

      Jan 21, 2023#2

      I recommend to read Running Restore User Customizations does not restore settings where I is explained that backup/restore user customizations or export/import settings cannot be used between different versions of UltraEdit and what are the reasons.

      There are two possibilities to migrate the macros and scripts from one PC with UltraEdit v24.10.0.23 to another PC with UltraEdit v2022.2.0.34.
      1. Copy all application data of UE v24.10.0.23 to the other PC and let UE v2022.2.0.34 update the configuration.
        1. Rename the directory %APPDATA%\IDMComp\UltraEdit on the PC with UE v2022.2.0.34 to UltraEditNew while not instance of UltraEdit is running.
        2. Copy the entire directory %APPDATA%\IDMComp\UltraEdit on the PC with UE v24.10.0.23 into the directory %APPDATA%\IDMComp on the PC with UE v2022.2.0.34.
        3. Start UE v2022.2.0.34 which recognizes the configuration files of UE v24.10.0.23 like uedit32u.ini or uedit64u.ini containing the configuration for macros and scripts and reads them. Exit UltraEdit to get the date from older version of UltraEdit written now into ue.ini and volatile\ue.vod which are used further by UE v2022.2.0.34. The older configuration files are never read again by UE v2022.2.0.34 and can be deleted now. That is like upgrading on same PC from UE v24.10.0.23 to v2022.2.0.34.
        4. UE v2022.2.0.34 reads the configuration data from the old configuration files and stores them in the new configuration files, but the syntax highlighting wordfiles and other user customizable files are not updated by UE v2022.2.0.34. It would be good to compare the folders UltraEdit and UltraEditNew and delete in UltraEdit and its subdirectories all files which do not exist in UltraEditNew, except the macro/script files, wordfiles, theme/layout files added by you in the past on the PC with UE v24.10.0.23, ue.uek if you made in UE v24.10.0.23 customizations on key assignments, etc. See the referenced topic where I explained which file in the application data directory or UE v28.10 contains which data. The set of configuration files has not changed much between UE v28.10 and v2022.2.
        5. Look on the files existing in both directory trees if there are some newer files to copy from UltraEditNew or one of its subdirectories to UltraEdit respectively the corresponding subdirectory. For example, if you edit in UltraEdit HTML and CSS files, it could be useful for you to copy UltraEditNew\wordfiles\css.uew over UltraEdit\wordfiles\css.uew because of this by default installed syntax highlighting wordfile is updated in UE v2022.2.0.34.
        6. Once finished with cleaning up the application data directory UltraEdit and its subdirectories from old configuration files no longer needed and all your macros and scripts, templates, syntax highlighting wordfiles, tag lists, layouts, themes, etc. are back and perhaps even updated by you, delete the directory UltraEditNew with the default configuration created by UE v2022.2.0.34 on a start with no directory UltraEdit in %APPDATA%\IDMComp.
      2. Migrate only the macro/script files and the configuration data for the macros and scripts.
        1. Copy just the file uedit32u.ini or uedit64u.ini in %APPDATA%\IDMComp\UltraEdit from PC with UE v24.10.0.23 to PC with UE v2022.2.0.34.
        2. Open the copied .ini file on the PC with UE v2022.2.0.34 in Windows Notepad.
        3. While no instance of UE v2022.2.0.34 is running, start a second Windows Notepad and open the file ue.vod in directory %APPDATA%\IDMComp\UltraEdit\volatile
        4. Copy from INI file of UE v24.10.0.23 to ue.vod of UE v2022.2.0.34 the sections [MacroAutoLoad] and [Scripting] with replacing these two sections in ue.vod on being already present in that file, save modified ue.vod and exit both Windows Notepad.
        5. Copy from PC with UE v24.10.0.23 to PC with UE v2022.2.0.34 all .mac macro files and all .js script files by replicating the directory structure(s) on PC with UE v2022.2.0.34.
        6. Start now UE v2022.2.0.34 and all macros and scripts should be available as long as the paths to the macro/script files is the same on both PCs.
      It is perhaps necessary to adapt the directory paths in file ue.vod with Windows Notepad while no instance of UE v2022.2.0.34 is running on macro/script files are stored in PC with UE v2022.2.0.34 not with the same directory path as on the PC with UE v24.10.0.23.

      I recommend to open each macro file once in UE v2022.2.0.34 and save the loaded macro(s) again into the macro file with same file name. The macro format changed also between UE v24.10.0.23 and UE v2022.2.0.34. The loading and saving of each macro file with UE v2022.2.0.34 results in updating the binary data in the macro files so that UE v2022.2.0.34 does not need to do that again on each future load of the macro files.
      Best regards from an UC/UE/UES for Windows user from Austria