[merlight]

Originally Posted by Argusus I have 4-5 of these scroll lists, and basically the same code to create each except for the container control and the sort keys that are needed to be unique, then after that when buildmasterlist, I access the saved variables to populate the scroll lists. I wonder how I could have all of my scroll lists share the same initialization code but have unique sort keys, and build master list, passing in unique containers you explained well.

Well, they have different row control template, default sort header, vastly different BuildMasterList, I think they deserve being separate classes. You can move a few things to a common base, like FilterScrollList and SortScrollList which are identical, and derive your special classes from that base.

local StuffListBase = ZO_SortFilterList:Subclass()
local CustomerList = StuffListBase:Subclass()
local XTradeItemsList = StuffListBase:Subclass()
...

My/TheirTradeItemsList look like they could be merged. Just pass the things that differ as additional arguments to initialize, and store them in the instance.

function XTradeItemsList:Initialize(control, itemsKey)
    StuffListBase.Initialize(self, control)
    self.itemsKey = itemsKey
    ...
end
 
function XTradeItemsList:BuildMasterList()
    ...
    for key, itemObject in pairs(selectedTrade[self.itemsKey]) do
        ...
    end
end
 
TRADESMAN.MyTradeItemsList = XTradeItemsList:New(MyTradeItemsContainer, "MyItems")
TRADESMAN.TheirTradeItemsList = XTradeItemsList:New(TheirTradeItemsContainer, "TheirItems")