Greetings,
Thank you for the continued developments of Wrye Bash.
I have encountered a couple of issues when using Wrye Bash v286 (SVN downloaded within the past 24 hours).
1.
Sub-package list/UI refresh performance issueEnabling/disabling a sub-package with an installer (archive/project) containing many files causes a greater delay during the UI refreshing process, than it did in v284.
With a complex installer containing 37,402 files, I observed refresh delays in v284 of ~1-2 seconds. In v286 (SVN), I observed refresh delays of ~7-8 seconds.
If required, I have provided an example archive installer with 200 sub-packages, each containing 1025 (0-byte) files; 205,000 in total.
Download link (113kB): http://www.sendspace.com/file/de91sj
My results for the test installerUI-refresh-time when changing a sub-package install state:
v284: ~3 s
v286: ~21 s
Feature proposalEven with v284 performance, selecting/deselecting hundreds of sub-packages could take many minutes, in part due to the automatic UI refresh.
An option to turn off automatic UI refresh could enable picking multiple sub-package options more efficiently. When done, the user could then toggle automatic UI refresh back on to update the UI.
2.
Custom Tool Launcher: Launch error of custom tools using "option switches", when the extension of the file to be launched is not entirely lowercase in Bash.iniExample:
sCustom1=OblivionModManager.EXEsCustom1opt=-bsa-browsersCustom1txt=OBMM BSA Browser
Results in error:
Traceback (most recent call last): File "C:\Oblivion\Mopy\basher.py", line 11355, in Execute os.startfile(self.exePath.s, (str(self.exeArgs))[2:-3])WindowsError: [Error 1155] No application is associated with the specified file for this operation: 'C:\\Oblivion\\OblivionModManager.EXE'
If option switches are omitted, then the program launches.
If the extension is entirely lowercase (sCustom1=OblivionModManager.
exe), then the program launches with option switches as expected.
_____
Precautionary notice regarding extracting test installer as a projectExtracting the contents of this test installer onto a NTFS volume can permanently inflate the "Master File Table" (MFT), (~200MB in my tests), if the volume has not at least previously held ~205,000 more files than what currently exist on that volume.
If one has a volume of such characteristics containing their "Bash Installers" directory, and wants to extract the test file as a project, and avoid an increase in MFT size of the volume, one could:
1. Create a temporary volume.
2a. Extract the test files to a temporary volume, then create a NTFS junction to the "Bash Installers" directory. (A tool like http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html can create/remove junctions via right-click menu.)
or 2b. Create "
:\Oblivion Mods\Bash Installers" directory, extract the test files as a project there, and modify the path of "sOblivionMods=" in Bash.ini to the new "Bash Installers" directory.
_____
Edit #1: Added notice regarding testing installer as a project.