1168 replies to this topic

[-Hurricane-]

I may have found another bug in the Extended Search function:
 

• Game: BGII:EE v1.3
• Launch the Extended Search
• Set resource type to ITM
• Select the item ability filter
• Select "Apply filters on a per ability basis"
• Set the ability type to Ranged (2)
• Under ability flags, select the "Add strength bonus" flag and leave "exact match" disabled
• Click "Search"

This should search for all throwing weapons that apply the strength bonus as part of their ranged ability.

However, you only get 7 results. The search seems to only include weapons that have at least one ability effect present in their ranged ability header. It does not include weapons that have no ability effects on their ranged ability. For example, the search finds ACIDOOZ3.itm, but not ACIDOOZ2.itm.

The dependency on the presence of an ability effect sounds somewhat similar to the previous Extended Search bug (http://www.shsforums...-21#entry575394). But I don't know if it's a regression or something else.

[Argent77]

I'll look into this. Actually, the Extended Search is a very complex beast and its flexibility is somewhat limited. I might implement an improved algorithm when I have the time for such a task.

You could always untick "Apply filters on a per ability basis" to include more matches, but you'd have to pick out a couple of mismatches.

[Tzarnal]

I have a bit of a feature request.  Although I realize you might not have an interest int it since it requires an external tool. However I'd like to see the ability to call a weidu --change-log for a file and have the result displayed within an NI window.

[Argent77]

I'd rather not add support for file formats that are not directly related to the Infinity Engine. Furthermore, WeiDU is still actively developed, which means that the format of the backup data generated by WeiDU may change anytime (it already has in the past). It would force me to keep NI up to date whenever WeiDU is updated. For the same reasons I also don't consider implementing WeiDU's D or TP2 file formats.

[Tzarnal]

Fair. Thank you for explaining at least.

Edited by Tzarnal, 07 August 2015 - 03:49 AM.

[Fiann of the Silver Hand]

This isn't a complaint or request.  When auto-indentation is turned off, it doesn't indent loaded scripts at all, but continues to auto-indent new lines after a carriage return.  So pretty much worse than before.  Weird behavior.

[Argent77]

Not sure what you mean. The cursor always jumps to the beginning of a line after pressing Enter/Return, unless you've added indentations on your own. It will preserve indentations of the previous line, but that's intended (and default) behavior of the text edit component. It shouldn't be an issue though, as long as you don't manually indent the code by yourself. Actually, this is the default behavior of all advanced text editors I've seen so far.

Edited by Argent77, 11 August 2015 - 02:27 AM.

[Fiann of the Silver Hand]

It will preserve indentations of the previous line, but that's intended (and default) behavior of the text edit component.

 

This is exactly and all I wanted to get rid of.  I use Notepad++, and disabling auto-indent does only that.

Edited by Fiann of the Silver Hand, 11 August 2015 - 02:35 AM.

[Argent77]

Shift+TAB works too for removing indentations. I'll think about disabling the auto-indent option of the edit component itself (if I can find out how).

[Fiann of the Silver Hand]

Don't even worry about it.  Like I said, I really need to not write scripts in NI anyway.  I can't imagine the multitude of code quirks to sort out for a tiny issue like this.  You do good work

[Argent77]

Disabling auto-indent was pretty much adding a single line of code. I had merely "fixed" it in the wrong file (hence my remark).

[cmorgan]

Heh! (By the way, thank you for expanding this tool - it is greatly appreciated. Things like the dialog tree structure, the ability to work on legacy BG all the way through BG2:EE, etc - I almost never use the actual editing tools, but just the ability to look at what is there and see how it is constructed, finding offsets, etc. - I have found it easier and easier to use to solve what I am trying to solve. So thank you!)

[Argent77]

Update: NearInfinity v1.36-20150826

Changes:

• Added option to select a user-defined font for displaying structured and textual resources (Options->Text Font->Select font...).
• Location flag descriptions of ARE resources can make use of custom entries found in AREATYPE.IDS when available.
• Unchecking Options->Text Editor->BCS and BAF->Enable Automatic Indentation now completely disables auto-indentation.
• Fixed encoding and decoding of (IWD2) script actions that require more than two string arguments.
• Fixed a regression which disabled storing settings of the Area Viewer.
• Missing IDS files don't cause scripts to produce errors.

Edited by Argent77, 26 August 2015 - 12:39 AM.

[Argent77]

Update: NearInfinity v1.36-20150827

A bugfix release:

• Fixed a bug in the initialization routine of the Extended Search dialog, which prevented the dialog from opening.

[Wisp]

Feature request: searching for references to this CRE among BCS (and probably also DLG) files should also match against script name and not only resref.

[Roxanne]

Feature request: searching for references to this CRE among BCS (and probably also DLG) files should also match against script name and not only resref.

Foolish me!!!! I only now realise the feature is not there, I never noticed because in most cre they are equal. So I did many searches with that tool in vain, wondering why it did not find what I was sure that it exists.

 

Yes,yes,yes to this request!!!

[Argent77]

Feature request: searching for references to this CRE among BCS (and probably also DLG) files should also match against script name and not only resref.

I fully agree. It'll be added in the next release.

Edited by Argent77, 30 August 2015 - 01:47 AM.

[Gwendolyne]

Update: NearInfinity v1.36-20150827

A bugfix release:

• Fixed a bug in the initialization routine of the Extended Search dialog, which prevented the dialog from opening.

 

Thanks!

I forgot to post about it before taking a few days break. I am back and it is already fixed!

[Fiann of the Silver Hand]

Could the MSECTYPE and MSCHOOL lists in the spell editor window be not all caps?  They were recently made all caps.

[Argent77]

That's because they were recently changed to use 2DA entries instead of hardcoded values. Converting everything into upper case is needed to remove inconsistencies and also to indicate that the entries are taken from an external resource.