Trying to optimise creation of buttons

[NinjoOnline]

What I currently have in my system is whenever a players inventory updates, I delete all the previous buttons in their backpack, and remake all of them. This seems really innefficient

function GetInventory.OnClientInvoke(inventory)
	PlayersInventory = inventory

	for _, button in pairs(Page:GetChildren()) do
		if button:IsA('ImageButton') then
			button:Destroy()
		end
	end

	createItems()
end

So I tried doing something like this

function GetInventory.OnClientInvoke(inventory)
	PlayersInventory = inventory

	for _, button in pairs(Page:GetChildren()) do
		if button:IsA('ImageButton') then
			for i, v in pairs(inventory) do
				if button.Name == i then
					button.Quantity.Text = v
					break
				end
			end
		end
	end
end

With the premise being if their is a button already of an item, it would just edit the quantity of the button, but I don’t know how to:

1. Check if button exists, but the player no longer has that item in their inventory (thus need to delete that set button)
2. Detect if there’s a new item in their inventory and no button for it, to create a button.

How I create the buttons too

local function createItems()
	if PlayersInventory then
		for i, v in pairs(PlayersInventory) do						
			local Button = CreateButton(i, 'Furniture', Page, v)
			
			local FurnitureItem = Furniture:FindFirstChild(i)
			
			Button.Activated:Connect(function()
				furnishButton(Button, FurnitureItem)
				Button:Destroy()
			end)
		end
	end
end

The players inventory looks like this too

Inventory = {
    ['Table'] = 4,
    ['Chair'] = 3,
    -- etc
}

[jakedies]

To check if the button exists, you can check if Page:FindFirstChild(name) is non-nil. To detect if a new item was added in their inventory, the easiest way would likely be to only allow mutation of the inventory through the use of setters (i.e. an AddItem method).

A general method if you don’t want to use setters would be to use metatables, the __newindex metamethod fires when a new key-value pair is added to a table. You can use that to create the button.

[azahid1]

GitHub - Roblox/rodux: A state management library for Roblox Lua inspired by...

Build GUIs with Roact & Rodux

What exactly is Roact and Rodux?

I’ve read several posts about this Roblox Library called Roact and how it’s similar to React JS, I however still don’t understand what Roact really is. I’ve seen other posts saying that they’ve used the said library in their plugin or interface for their game, so is this library more of the scripting aspect or interface design aspect? I have three questions to ask: Is Roact and Rodux the same thing? What is this specifically used for? How to use these libraries?

https://github.com/Roblox/react

Rocrastinate: a Roact/Rodux-like Library Optimized for Roblox

on that same note, here 3 reasons why you should definitely use roact & rodux long term support from roblox engineers roact and rodux are being adopted as the standard for all of the in-engine UI development at the company. the entire roblox mobile app was completely written using roblox’s UI elements, lua, and roact/rodux. new tools and features are in constant development for these systems because internally, engineers are dependent on them. pain points will be located and ironed out, syste…

[RainScripts]

For your table items, i’d do this instead

[‘Table’] = {‘Table’, 4} --TableItem
[‘Chair’] ={‘Chair’, 3) --TableItem

Then, for the update function it would loop through the Inventory table, and for each item in the table, if it didn’t find TableItem[1] but it was in their inventory table, then it would give them a new button.

As for updating the buttons when something is removed from the table, i’d just find a way to make the buttons slide down in position (or over?). Or, you can just keep updating and deleting and adding all of the buttons again, which isn’t the greatest, but hey, it works.