Two (^2) quick ones :
1) What exactly is solid compression ?
2) When I right click on a project and choose "Pack to archive" what are the options that are used - I never use this feature cause I am not sure it follows http://www.bild.me/bild.php?file=19472647zOptions.jpg (btw I have found no clear explanation on 7z's compression options when I once tried googling them - if anyone could post a link I'd thank him much for that)
3)Is there an option to disable :
---------------------------Hide Files---------------------------Hide these files? Note that hidden files are simply moved to the Bash\Hidden subdirectory.---------------------------Yes No ---------------------------
4) Lastly - does the PM tab work with the new forum ?
thanks
1) Using solid compression means that the file will be smaller on the disk, but that the entire file has to be extracted even if you just want to get the readme. With non-solid compression, the readme could be extracted without having to extract everything else too. So using solid compression will save disk space, but mean that things like annealing the package will take longer.
2) This is the command line that Bash uses "7z.exe a "DESTNAME" -tARCHIVETYPE -ms=SOLID -y -r -o"OUTPUTDIR" -i!"PROJECTPATH\\*" -x@FILELIST -scsWIN" where DESTNAME is the name of the archive to create, ARCHIVETYPE is the extension of the archive to create, SOLID is either "off" or "on" depending on if you use solid compression, OUTPUTDIR is the installers directory, PROJECTPATH is the path to the project, and FILELIST is a text file with a list of files to include.
3) Not sure what you mean. Disable the ability to hide files? Just disable that prompt? In both cases, there is not an option to do so.
4) I honestly don't know. I don't use that feature that often, and the last time I used it was before the boards switched over. Best I can say is to give it a try, and report here if it doesn't work.
On new OB install, I got this error when I try to build the bashed patch.
WB version is listed as 286 (install + latest SVN), the error appeared also in 285, and with cbash on and off.
What's is this "Full must be non-zero" error? I know that it must be because a mistake on my side, but I am unable to find it, so any hint would be appreciated :shrug:
It's related to the Import Actors: AIPackages. That's something PacificMorrowind worked on. Hrm...a quick guess would be that you have that import active, but there aren't any files that are actually being imported.
I'm surprised that your patch involves regular expressions and escaping of non-ASCII characters. I had figured the solution for Bash's path handling would be to convert it to consistently use Unicode strings instead of byte strings for all paths and filenames, and to ask users to install the Unicode version of wxPython instead of the ANSI version. The Windows API supports Unicode natively, including for file I/O operations, and if Bash can utilize that, non-ASCII characters shouldn't need any special handling.
Yeah, that would be the more proper solution. That's a lot of work though, and would require reviewing the entirety of Bash. For now, I'd be happy with anything that helps.