-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Tested with many extensions, and with only this one alone. The same behavior is observed. (v. 1.21 from GitHub)
With this extension loaded...
- Create a [I]Container[/I] entry in the PC inventory
- Add an [I]Item[/I] to the PC inventory and add the [I]ContainerName[/I] to the [I]Location[/I] field
- Double click the [I]Container[/I] to collapse it
- This does collapse it, and adds a [B][+][/B] to the Container's name.
- Double-click again to expand the container, and the [+] is removed
- This moves the location (makes sense, it always did...resorting alphabetically with the [+] and without.
Only, here's the issue I'm seeing:
- For this example, I am using [I]0. ACTION ONLY (bag)[/I] (where I store an [I]Improvised Weapon[/I], [I]Unarmed Attack[/I], and [I]Shield Bash[/I] item - so they appear in the Weapon List for the character. Though the same happens in more traditional containers too.
- I assign [I]0. ACTION ONLY (bag)[/I] as the location for the [I]Shield Bash[/I] item
- The inventory UX successfully shifts the item from its purely alphabetical location, it appears under the [I]0. ACTION ONLY (bag)[/I] entry as desired.
- I double-click the container to collapse it
- As note above, it amends the ContainerName with the [B][+][/B] as if it were collapsed, but does not also amend the name for that entry in the Location column for assigned items.
- As such, the associated item is still looking (it appears) for the name without the [+] and does not "collapse into" the container. If memory serves, the [+] didn't get amended to the individual item entry locations in the past...my suspicion is that the sorting previously ignored the [+].
- If I manually add [+] to LocationName in the Location field for the item it will accurately [I]sort [/I]it to be under and indented as "belonging" to the container...but it's still [I]visible [/I]in the inventory list. It doesn't actually collapse or hide inventory.
I hope this helps. :(
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels