("WIP" means Work In Progress.)
So, some of you may have noticed that I've been working on this big thing for a while now, which I'm planning on sharing. In some places I've even shared my "To Do" list and such. Well I'm getting close, which could be 1-3 months, and I just thought it'd beneficial to get some feedback on how other people would want to use it. Though there's a lot of stuff I need to code before I even start thinking about something user friendly, it'd be mutually beneficial if people would share what they'd like for the script to be able to accomplish. That way I can make sure that I keep those things in mind as I'm coding all the logic. Said another way, "How would you want to use this?"

So let's start by establishing some common terms for the Inventory Window.



Left Pane contains: IndexButton, ContainerList, and ContainerLines (expandable)
Right Pane contains: ListViewButton (only view I plan to use), CapacityUtilized, Filter, ContainerItemsTable (linked to ContainerLine in Left Pane)

The Goal: To Forge One Item Window To Rule Them All! Everything item related can happen in one window.

It can already select any ContainerLine (LeftPane) and filter/read the contents, which can include the item's name, volume, and everything else. (Though easy, still have to code the parsing logic so that the read stores the item objects as individual lines containing all the attributes.)

Moving items will be accomplished by:
Opening/Selecting the ContainerLine (LeftPane) to display the table (in RightPane) that has the items you want to withdraw.
Expanding the ContainerLines (LeftPane) to display so that the destination container is visible.
Selecting the requested lines in the Right Pane (withdraw) table.
Dragging the selected lines from the withdraw table onto the LeftPane ContainerLine where you want the items deposited.

Example of what I'm going to make sure the following is possible (not saying it'll work exactly like this...) "Select [specified ContainerLine], filter by [filterText], read contents, select [All/Specified] lines, click/drag to move them to different container line on left." (No idea how I'm going to make that user friendly though, LOL!)

My To Do List:
LeftPane:
Index Button (Added but not used yet)
Container List (VERY COMPLEX, maybe 25% done. Un-optimized foundation code.)
My Filters (Optional)
Item Filters + Button (Optional)

RightPane:
ExpandCollapse Arrows (Knows they're there but doesn't use the yet, but soon...ish)
Back Button (Optional)
Forward Button (Optional)
Table Icon Only Button (Not Used)
Table Icon Details Button (Optional)
Table List Only Button
Container Capacity Utilized
Filter
Table (Need to add logic for storing cell contents in linked lists once Table Headers works.)
Table Headers (Working on it. Need to add this as check to see if in correct view, which is List Only.)
Table List (Only List Only mode)
Loot All (Optional, but will probably add this eventually)

Reserved

(Also, I just binge-coded about 500 lines without testing it and am so afraid to test it that I'm just continuing to code... )
Debugging it wasn't bad!

The containerList is incredibly more complex than anything I've had to code for before. I'm up to 850 lines and have not finished the algorithm for getting the line coordinates. But I did figure out how to do it. Now I just need to code it.

; Container/Cargo/Inventory left list is has special spacing criteria
; Expandable Line Sections: Inventory Lists Only
; Tracking whether a line us within an expanded container is tricky because there are no line dividers and open subcontainers add a few buffer pixels at the end of each level. More difficult to predict where each should be found.
; look for text. Not a good idea because text can change and not efficient. Has to be checked each time something changes.
; Could collapse all arrows and get a main level baseline
; Only ever have one container expaned at a time?
; Could do some bottom up pixel search detecting the text colors, maybe: (PixelsBetween -2 ) / 4
; Use Icons. Innacurate as they have different dimensions, but may be easier to implement initially. A bit less inefficient, but also has to be checked each time something changes.
; BufferAfterLineLevels := 4 * LevelDifference + 2 Separators buffer after the final entry for the level. Much more efficient, but could be complicated. (Sounds like fun, but wait to see if it is needed.))
; Arrows indicate the line expands and whether it is expanded. Use icons to know what is in each line.
; Would have to track expanded arrows above
; Problem is when a sub-level line is above a main level line, where the main line doesn't have an arrow (Can, Hangar, ItemHanger that doesn't have expandable items in it.)
; Easiest would be to do an image search/click for what you want, making sure that necessary things are expanded via same method

All hail innominate and Slav2 for their work on EP

I just found out I'm moving in a month. So with packing/moving and settling back in, my timeline is going to get pushed back 1-3 months.

Good luck in your new place! "Fly safe"!

And if you need someone to test anything just ask, I could do a lot of testing if needed. Best Regards!