Ok. Thank you for the help guys. I think I finally figured out what is going on. First here's the code:
Code: Select all
local l_player = game.players[event.element.player_index]
local s_stack = l_player.cursor_stack
...
if s_stack and s_stack.valid_for_read and s_stack.type == "blueprint" and s_stack.is_blueprint_setup() then
...
if #s_stack.blueprint_icons > 0 then
local icon_quad = l_schematic.add{type="table", name="icons", colspan=2, style="slot_table_style"}
for ii, iv in ipairs(s_stack.blueprint_icons) do
icon_quad.add{type="button", name="icon_"..iv.name, style="bpr_gs_"..iv.name.."_small"}
end
else
l_schematic.add{type="label", name="icons", caption="WTF"}
end
...
end
PSEUDO:
1. Get the players cursor_stack
2. Check that it is a blueprint
3a. Try to add the blueprint icons as little icon/buttons to a custom gui element, or
3b. (when 3a fails) just add a label element that says "WTF"
*. The result is "WTF" whenever it is a blueprint with one icon
So, in a nutsack, "#s_stack.blueprint_icons" is returning '0', which I think means it is trying to say the 0th element has the icon, not that there are no icons; and, yes, when I access "s_stack.blueprint_icons[0]" it does indeed return the proper icon. My only problem then is how to tell the difference between 0 icons and icons[0]. Also, this breaks the "ipairs" for loop, which will just do 0 iterations.
Solution:
I just switched it to a standard "pairs" for loop (even though it is supposed to be an array
), and it works.
Code: Select all
for ik, iv in pairs(s_stack.blueprint_icons) do
icon_quad.add{type="button",
name="icon_"..iv.name,
style="bpr_gs_"..iv.name.."_small"}
end
So for me, I guess problem solved although you Devs may feel different; at least there is a workaround.
...this did bring a different issue to light though, but I will make a separate thread for that potential bug.
