Writing Out Multiple Tables

buttonTable[name].xMin = xMin

tNames = {
[1] = {
name = "Hellkid98(me)",
age = 15,
},

[2] = {
name = "Someone",
age = "Unknown",
},
}

for i = 1,#tNames do
print(tNames[i].name.."  Age: "..tNames[i].age)
end

tPersons = {
["Ryan"] = {
name = "Ryan",
age = 17,
},

["Harold"] = {
name = "Harold"
age = 45,
},
}

print(tPersons["Ryan"].name.."  Age: "..tPersons["Ryan"].age)

Hellkid98, on 28 July 2013 - 03:59 PM said:

Do you mean something like this? .-.

buttonTable[name].xMin = xMin

An example

tNames = {
[1] = {
name = "Hellkid98(me)",
age = 15,
},

[2] = {
name = "Someone",
age = "Unknown",
},
}

for i = 1,#tNames do
print(tNames[i].name.."  Age: "..tNames[i].age)
end

In your case when you use a name index for table

tPersons = {
["Ryan"] = {
name = "Ryan",
age = 17,
},

["Harold"] = {
name = "Harold"
age = 45,
},
}

print(tPersons["Ryan"].name.."  Age: "..tPersons["Ryan"].age)

for key, value in paris(buttonTable) do
    print(textutils.unserialize(value))
end

buttons = {}

function createButton(sX,fX,y)
nButton = {}
nButton.sX = sX
nButton.fX = fX
nButton.y = y

table.insert(buttons,nButton)
end

function buttonTableTable(name, xMin, xMax, yMin, yMax, text)
buttonTable[name]["active"] = false
buttonTable[name]["xMin"] = xMin
buttonTable[name]["xMax"] = xMax
buttonTable[name]["yMin"] = yMin
buttonTable[name]["yMax"] = yMax
buttonTable[name]["text"] = text
x,y = mon.getScreenSize()
if (xMin or xMax) > x then
  print(fault.outOfBounds)
elseif (xMin or xMax) < x then
  print(fault.outOfBounds)
elseif (yMin or yMax) > y then
  print(fault.outOfBounds)
elseif (yMin or yMax) < y then
  print(fault.outOfBounds)
else
  xText = math.floor((((buttonTable[name]["xMin"] + buttonTable[name]["xMax"])-string.len(buttonTable[name]["text"]))/2)+1)
  yText = math.floor((buttonTable[name]["yMin"] + buttonTable[name]["yMax"])/2)
  mon.setBackgroundColor(16384)
  for i = yMin, yMax do
   for j = xMin, xMax do
    if (i == yText and j == xText) then
	 mon.write(buttonTable[name]["text"])
    else
	 mon.write(" ")
    end
   end
  end
end
end

Hellkid98, on 29 July 2013 - 07:39 AM said:

Then I'm guessing you have a function to create buttons?

buttons = {}

function createButton(sX,fX,y)
nButton = {}
nButton.sX = sX
nButton.fX = fX
nButton.y = y

table.insert(buttons,nButton)
end

You should show us the full code you have

function buttonTableTable(name, xMin, xMax, yMin, yMax, text)
buttonTable[name].active = false
buttonTable[name].xMin = xMin
buttonTable[name].xMax = xMax
buttonTable[name].yMin = yMin
buttonTable[name].yMax = yMax
buttonTable[name].text = text
x,y = mon.getScreenSize()
if (xMin or xMax) > x then
  print(fault.outOfBounds)
elseif (xMin or xMax) < x then
  print(fault.outOfBounds)
elseif (yMin or yMax) > y then
  print(fault.outOfBounds)
elseif (yMin or yMax) < y then
  print(fault.outOfBounds)
else
  xText = math.floor((((buttonTable[name].xMin + buttonTable[name].xMax)-string.len(buttonTable[name].text))/2)+1)
  yText = math.floor((buttonTable[name]yMin + buttonTable[name].yMax)/2)
  mon.setBackgroundColor(16384)
  for i = yMin, yMax do
   for j = xMin, xMax do
    if (i == yText and j == xText) then
     mon.write(buttonTable[name].text)
    else
     mon.write(" ")
    end
   end
  end
end
end

tNumbers = {
["One"] = {
num = 1,
},

["Two"] = {
num = 2,
["addTwo"] = { num = 2 + 2,},
},
}

--[[
When you are trying to print(buttonTable[name]["xMin"])
You are trying to print the table inside the table with the name
And the table would kinda look like this

buttonTable = {
["SomeName"] = {
["xMin"] = { 12,}
},
}

But you are meaning todo this
buttonTable = {
["SomeName"] = {
xMin = 12,
xMax = 20,
text = "Hello",
},
}

print(buttonTable["SomeName"].text)
-- This would print Hello

]]--

function buttonTableTable(name, xMin, xMax, yMin, yMax, text)
buttonTable[name]["active"] = false
buttonTable[name]["xMin"] = xMin
buttonTable[name]["xMax"] = xMax
buttonTable[name]["yMin"] = yMin
buttonTable[name]["yMax"] = yMax
buttonTable[name]["text"] = text
x,y = mon.getScreenSize()
if (xMin or xMax) > x then
  print(fault.outOfBounds)
elseif (xMin or xMax) < x then
  print(fault.outOfBounds)
elseif (yMin or yMax) > y then
  print(fault.outOfBounds)
elseif (yMin or yMax) < y then
  print(fault.outOfBounds)
else
  xText = math.floor((((buttonTable[name]["xMin"] + buttonTable[name]["xMax"])-string.len(buttonTable[name]["text"]))/2)+1)
  yText = math.floor((buttonTable[name]["yMin"] + buttonTable[name]["yMax"])/2)
  mon.setBackgroundColor(16384)
  for i = yMin, yMax do
   for j = xMin, xMax do
    if (i == yText and j == xText) then
	 mon.write(buttonTable[name]["text"])
    else
	 mon.write(" ")
    end
   end
  end
end
end

Bubba, on 30 July 2013 - 01:47 PM said:

What exactly is your question? I mean I know that you say the problem is getting the button array on the screen, but are you asking for help going through each button and drawing it on the screen or are you actually encountering errors?

GamerNebulae, on 30 July 2013 - 01:54 PM said:

My problem is, that whenever there are multiple buttons, I have no clue how to draw them all. I know how to draw one, but not multiple ones.

local buttonTable = {}

local function addButton(...)
  table.insert(buttonTable, {...}) --#You may want to consider doing it this way. It makes things considerably easier :)/>/>
end

local function drawButton(btn)
  --#You know how to handle drawing an individual button
  term.setCursorPos(btn[1],btn[2]) --#Sure, not quite as readable my way, but it is quite a bit shorter and you don't have to mess around with inserting names into the button table
  term.write(btn[3])
end

local function drawAllButtons()
  for buttonIndex, btn in pairs(buttonTable) do --#Just iterate over every button and draw it with the drawButton function
    drawButton(btn)
  end
end

Bubba, on 30 July 2013 - 01:58 PM said:

GamerNebulae, on 30 July 2013 - 01:54 PM said:

My problem is, that whenever there are multiple buttons, I have no clue how to draw them all. I know how to draw one, but not multiple ones.

Well you're actually pretty close already. All you need is a function to draw each button individually and then loop over the table that stores your buttons. For example:

local buttonTable = {}

local function addButton(...)
  table.insert(buttonTable, {...}) --#You may want to consider doing it this way. It makes things considerably easier :)/>/>/>
end

local function drawButton(btn)
  --#You know how to handle drawing an individual button
  term.setCursorPos(btn[1],btn[2]) --#Sure, not quite as readable my way, but it is quite a bit shorter and you don't have to mess around with inserting names into the button table
  term.write(btn[3])
end

local function drawAllButtons()
  for buttonIndex, btn in pairs(buttonTable) do --#Just iterate over every button and draw it with the drawButton function
	drawButton(btn)
  end
end

Is this what you're looking for?

GamerNebulae, on 30 July 2013 - 02:34 PM said:

Can you maybe plug into the code I have now? It feels quite alien for me. I would like to keep it the way it is now, because as I said: I want to keep it a simple API for every CC-user to use.

GamerNebulae, on 30 July 2013 - 02:41 PM said:

The way how you iterate through the tables is the part where I get confused. For the rest I understand almost everything.

some_table = {
  [1] = "Hello!",
  [2] = "Goodbye!"
}

for index, value in pairs(some_table) do
  print(index..": "..value)
end

Bubba, on 30 July 2013 - 02:57 PM said:

GamerNebulae, on 30 July 2013 - 02:41 PM said:

The way how you iterate through the tables is the part where I get confused. For the rest I understand almost everything.

You mean a for x,y in pairs loop? Here is a link to Programming in Lua which might help you out with that.

Basically though, a pairs loop just goes through every single item in a table and assigns the index of the item to the first argument and the value of the item to the second. So for example:

some_table = {
  [1] = "Hello!",
  [2] = "Goodbye!"
}

for index, value in pairs(some_table) do
  print(index..": "..value)
end

The above code could output:
1: Hello
2: Goodbye
or
2: Goodbye
1: Hello

Due to the fact that pairs does not go in any specific order but rather gets the indexes at "random".

for name, iterations in pairs(buttonTable) do
	for y = buttonTable[name]["yMin"], buttonTable[name]["yMax"] do
		for x = buttonTable[name]["xMin"], buttonTable[name]["xMax"] do
			etc...
		end
	end
end

Bubba, on 30 July 2013 - 02:57 PM said:

GamerNebulae, on 30 July 2013 - 02:41 PM said:

The way how you iterate through the tables is the part where I get confused. For the rest I understand almost everything.

You mean a for x,y in pairs loop? Here is a link to Programming in Lua which might help you out with that.

Basically though, a pairs loop just goes through every single item in a table and assigns the index of the item to the first argument and the value of the item to the second. So for example:

some_table = {
  [1] = "Hello!",
  [2] = "Goodbye!"
}

for index, value in pairs(some_table) do
  print(index..": "..value)
end

The above code could output:
1: Hello
2: Goodbye
or
2: Goodbye
1: Hello

Due to the fact that pairs does not go in any specific order but rather gets the indexes at "random".

Hellkid98, on 30 July 2013 - 04:34 PM said:

Bubba, on 30 July 2013 - 02:57 PM said:

GamerNebulae, on 30 July 2013 - 02:41 PM said:

The way how you iterate through the tables is the part where I get confused. For the rest I understand almost everything.

You mean a for x,y in pairs loop? Here is a link to Programming in Lua which might help you out with that.

Basically though, a pairs loop just goes through every single item in a table and assigns the index of the item to the first argument and the value of the item to the second. So for example:

some_table = {
  [1] = "Hello!",
  [2] = "Goodbye!"
}

for index, value in pairs(some_table) do
  print(index..": "..value)
end

The above code could output:
1: Hello
2: Goodbye
or
2: Goodbye
1: Hello

Due to the fact that pairs does not go in any specific order but rather gets the indexes at "random".

Wouldn't ipairs go in order? .-.

Hellkid98, on 30 July 2013 - 04:34 PM said:

Wouldn't ipairs go in order? .-.

LBPHacker, on 30 July 2013 - 04:52 PM said:

Hellkid98, on 30 July 2013 - 04:34 PM said:

Wouldn't ipairs go in order? .-.

It would. But it would iterate through the numeric indices only.

local t = {
  "this",
  key = "value",
  ["some key"] = "some value",
  "that",
  [5] = "the other",
}

for i,v in ipairs(t) do
  print( i.." : "..v )
end

1 : this
2 : that

for k,v in pairs(t) do
  print( k.." : "..v )
end

1 : this
2 : that
5 : the other
some key : some value
key : value

theoriginalbit, on 30 July 2013 - 06:29 PM said:

The thing to remember is that ipairs will only iterate sequential numerical indexes and it will be in order. However pairs will not have any order for the key/value pairs, but numerical indexes are iterated first AND in order!

Example:

Assume we have this table

local t = {
  "this",
  key = "value",
  ["some key"] = "some value",
  "that",
  [5] = "the other",
}

ipairs loop

for i,v in ipairs(t) do
  print( i.." : "..v )
end

will output

1 : this
2 : that

pairs loop

for k,v in pairs(t) do
  print( k.." : "..v )
end

will output

1 : this
2 : that
5 : the other
some key : some value
key : value

NOTE: the key/value pairs may be in a different order, i didn't actually run this code, it should be noted that it can be in any order (not alphabetical or adding order) but each time you iterate it will be in the same order as previous times.

GamerNebulae, on 31 July 2013 - 05:23 AM said:

the first element in the array

for key, value in pairs(buttonTable) do
    -- key is a string: contains the name of the button
    -- value is a table: contains the information accosiated with the button
end

LBPHacker, on 31 July 2013 - 05:36 AM said:

GamerNebulae, on 31 July 2013 - 05:23 AM said:

the first element in the array

The first dimension, you mean? Still use pairs:

for key, value in pairs(buttonTable) do
	-- key is a string: contains the name of the button
	-- value is a table: contains the information accosiated with the button
end

for name, value in pairs(buttonTable) do
	    for y = buttonTable[name]["yMin"], buttonTable[name]["yMax"] do
			    for x = buttonTable[name]["xMin"], buttonTable[name]["xMax"] do
					    etc...
			    end
	    end
end

GamerNebulae, on 31 July 2013 - 05:39 AM said:

If I grab my code from earlier on and redesign it a bit, should it work?

LBPHacker, on 31 July 2013 - 05:59 AM said:

GamerNebulae, on 31 July 2013 - 05:39 AM said:

If I grab my code from earlier on and redesign it a bit, should it work?

Sure it should. Although since value essentially contains buttonTable[name], you could replace every occurence of buttonTable[name] with value.

for value, name in pairs(buttonTable) do
end

LBPHacker, on 31 July 2013 - 06:24 AM said:

Nope. The loop is fine as it is. Just replace "buttonTable[name]" with "value" INSIDE the loop, because they hold the same table. But leave the "name, value" part as it is. Even if you don't use "name", it has to be there.

GamerNebulae, on 31 July 2013 - 06:41 AM said:

Can you give an example how it would work in my code?

for name, value in pairs(buttonTable) do
  for y = value["yMin"], value["yMax"] do
	for x = value["xMin"], value["xMax"] do
	  etc...
	end
  end
end

for name, value in pairs(buttonTable) do
    for y = buttonTable[name]["yMin"], buttonTable[name]["yMax"] do
        for x = buttonTable[name]["xMin"], buttonTable[name]["xMax"] do
            etc...
        end
    end
end

for name, value in pairs(buttonTable) do
    for y = value["yMin"], value["yMax"] do
        for x = value["xMin"], value["xMax"] do
            etc...
        end
    end
end

LBPHacker, on 31 July 2013 - 06:56 AM said:

EDIT: HOLY CRAP Bit that was fast! (been ninja'd)

Well, this is your code, right?

for name, value in pairs(buttonTable) do
	for y = buttonTable[name]["yMin"], buttonTable[name]["yMax"] do
		for x = buttonTable[name]["xMin"], buttonTable[name]["xMax"] do
			etc...
		end
	end
end

Now replace every "buttonTable[name]" with "value":

for name, value in pairs(buttonTable) do
	for y = value["yMin"], value["yMax"] do
		for x = value["xMin"], value["xMax"] do
			etc...
		end
	end
end

GamerNebulae, on 31 July 2013 - 07:00 AM said:

LBPHacker, on 31 July 2013 - 06:56 AM said:

EDIT: HOLY CRAP Bit that was fast! (been ninja'd)

Well, this is your code, right?

for name, value in pairs(buttonTable) do
	for y = buttonTable[name]["yMin"], buttonTable[name]["yMax"] do
		for x = buttonTable[name]["xMin"], buttonTable[name]["xMax"] do
			etc...
		end
	end
end

Now replace every "buttonTable[name]" with "value":

for name, value in pairs(buttonTable) do
	for y = value["yMin"], value["yMax"] do
		for x = value["xMin"], value["xMax"] do
			etc...
		end
	end
end

Okay and just for esthetics, can I turn value and name around? It just looks cleaner ^^

theoriginalbit, on 31 July 2013 - 06:56 AM said:

GamerNebulae, on 31 July 2013 - 06:41 AM said:

Can you give an example how it would work in my code?

for name, value in pairs(buttonTable) do
  for y = value["yMin"], value["yMax"] do
	for x = value["xMin"], value["xMax"] do
	  etc...
	end
  end
end

EDIT: haha! I'm a ninja! :ph34r:/>

LBPHacker, on 31 July 2013 - 06:56 AM said:

EDIT: HOLY CRAP Bit that was fast! (been ninja'd)

Well, this is your code, right?

for name, value in pairs(buttonTable) do
	for y = buttonTable[name]["yMin"], buttonTable[name]["yMax"] do
		for x = buttonTable[name]["xMin"], buttonTable[name]["xMax"] do
			etc...
		end
	end
end

Now replace every "buttonTable[name]" with "value":

for name, value in pairs(buttonTable) do
	for y = value["yMin"], value["yMax"] do
		for x = value["xMin"], value["xMax"] do
			etc...
		end
	end
end

for name, button in pairs(buttonTable) do
    for i = button["yMin"], button["yMax"] do
	    for j = button["xMin"], button["xMax"] do
		    if (i == yText and j == xText) then
			    mon.write(button["text"])
		    else
			    mon.write(" ")
		    end
	    end
    end
end

GamerNebulae, on 31 July 2013 - 07:50 AM said:

Maybe any ideas for the interactive part? Like I said, I want this to be a API that can be used by ANYONE. No matter how experienced they are in CC.

theoriginalbit, on 31 July 2013 - 08:04 AM said:

GamerNebulae, on 31 July 2013 - 07:50 AM said:

Maybe any ideas for the interactive part? Like I said, I want this to be a API that can be used by ANYONE. No matter how experienced they are in CC.

They shouldn't need to change any of that code… No matter their experience in CC… The point of APIs is to supply an interface to a program you have created, or create a section of useful functions, etc… They shouldn't need to be modified… They can have different data (i.e. buttons) but the functions shouldn't need to change…

Lyqyd, on 31 July 2013 - 02:46 PM said:

Well, logically, you need a way to determine whether or not a click occurred in a specific area. This means that it must have occurred between the top and the bottom, and also between the left side and the right side. You will need to check that the click occurred to the right of the left edge, and also to the left of the right edge. Same with top and bottom.

Hint: one if statement with four comparisons joined by three ands.

while true do
  event, side, xPos, yPos = os.pullEvent()
    if event == os.pullEvent("monitor_touch") then
	  if (buttonTable[name]["xMin"] >= xPos and buttonTable[name]["xMax"] <= xPos and buttonTable[name]["yMin"] >= yPos and buttonTable[name]["yMax"] <= yPos) then
	  end
    end
end

GamerNebulae, on 31 July 2013 - 03:33 PM said:

Would this do?

while true do
  event, side, xPos, yPos = os.pullEvent()
    if event == os.pullEvent("monitor_touch") then
	  if (buttonTable[name]["xMin"] >= xPos and buttonTable[name]["xMax"] <= xPos and buttonTable[name]["yMin"] >= yPos and buttonTable[name]["yMax"] <= yPos) then
	  end
    end
end

if (5 >= 6 and 20 <= 6 and 10 >= 11 and 9 <= 11) then
  --#All of these evaluate false despite the fact that the click was inside

Bubba, on 31 July 2013 - 04:22 PM said:

GamerNebulae, on 31 July 2013 - 03:33 PM said:

Would this do?

while true do
  event, side, xPos, yPos = os.pullEvent()
	if event == os.pullEvent("monitor_touch") then
	  if (buttonTable[name]["xMin"] >= xPos and buttonTable[name]["xMax"] <= xPos and buttonTable[name]["yMin"] >= yPos and buttonTable[name]["yMax"] <= yPos) then
	  end
	end
end

Close. Check your if statement again. You've reversed the comparisons. That would evaluate true if the user clicked anywhere but on the button.

e.g. Button at (5,10) with a width of 15 and height of 3
Click at 6,11

if (5 >= 6 and 20 <= 6 and 10 >= 11 and 9 <= 11) then
  --#All of these evaluate false despite the fact that the click was inside

while true do
  if (xPos >= buttonTable[name]["xMin"] and xPos <= buttonTable[name]["xMax"] and yPos >= buttonTable[name]["yMin"] and yPos <= buttonTable[name]["yMax"]) then
    action...
  end
end

Lyqyd, on 31 July 2013 - 06:43 PM said:

Yep, that looks correct. Obviously, though, you'd need something to pull the event to generate xPos and yPos, like you had in the previous snippet, but your if statement appears to be correct this time.

local function getClicked( xPos, yPos )
  if not (xPos and yPos) then
    error("expected number, got nil")
  end
  --Change the "buttons" part to the name of the array your using
  for name,_ in pairs(buttons) do
    if (xPos >= buttonTable[name]["xMin"] and xPos <= buttonTable[name]["xMax"] and yPos >= buttonTable[name]["yMin"] and yPos <= buttonTable[name]["yMax"]) then
    return name
  end
end

local _,_,x,y = os.pullEvent("mouse_click")
local pressed = getClicked(x,y)

if pressed == "shutdown" then
  os.shutdown()
elseif pressed == "turtleon" then
  rednet.send(12,"start")
end

Apemanzilla, on 01 August 2013 - 07:05 AM said:

local function getClicked( xPos, yPos )
  if not (xPos and yPos) then
	error("expected number, got nil")
  end
  --Change the "buttons" part to the name of the array your using
  for name,_ in pairs(buttons) do
	if (xPos >= buttonTable[name]["xMin"] and xPos <= buttonTable[name]["xMax"] and yPos >= buttonTable[name]["yMin"] and yPos <= buttonTable[name]["yMax"]) then
	return name
  end
end

Basic usage:

local _,_,x,y = os.pullEvent("mouse_click")
local pressed = getClicked(x,y)

Somewhere below that you can use a row of if statements to determine what to do:

if pressed == "shutdown" then
  os.shutdown()
elseif pressed == "turtleon" then
  rednet.send(12,"start")
end

Change the conditions and actions to match your needs.

button(..........., function())

while true do
  event, side, xPos, yPos = os.pullEvent()
  if event == "monitor_touch" then
	if (xPos >= buttonTable[name]["xMin"] and xPos <= buttonTable[name]["xMax"] and yPos >= buttonTable[name]["yMin"] and yPos <= buttonTable[name]["yMax"]) then
	  buttonTable[name]["action"]
	end
  end
end

function test()
 print("Hello World!")
end

tFunction = {
[1] = {
name = test,
},
}

functionName = tFunction[1].name
functionName()

Hellkid98, on 01 August 2013 - 09:16 AM said:

Do you mean that you want to call a function from a table?

function test()
print("Hello World!")
end

tFunction = {
[1] = {
name = test,
},
}

functionName = tFunction[1].name
functionName()

os.loadAPI("monitor")
monitor.button("buttonOne", 3, 26, 2, 11, "button", colors.cyan, "pulse", "left", 5)

GamerNebulae, on 01 August 2013 - 07:18 PM said:

New problem! I tried to use the API by using this code:

os.loadAPI("monitor")
monitor.button("buttonOne", 3, 26, 2, 11, "button", colors.cyan, "pulse", "left", 5)

I got this error: monitor:33: index expected, got nil
Here is the code on pastebin: http://pastebin.com/kG0hxGhG
The code is far from done, but I'll finish it.

people = {}

people["Bubba"]["Name"] = "Bubba"
people["Bubba"]["Height"] = "5'11\""

people["Bubba"] = {}
people["Bubba"]["Name"] = "Bubba"
people["Bubba"]["Height"] = "5'11\""

function button(name, xMin, xMax, yMin, yMax, text, colorButton, action, parameterOne, parameterTwo, parameterThree)
        clear()
    buttonTable[name]["xMin"] = xMin
    buttonTable[name]["xMax"] = xMax
    buttonTable[name]["yMin"] = yMin
    buttonTable[name]["yMax"] = yMax
...

theoriginalbit, on 30 July 2013 - 06:29 PM said:

The thing to remember is that ipairs will only iterate sequential numerical indexes and it will be in order. However pairs will not have any order for the key/value pairs, but numerical indexes are iterated first AND in order!

Symmetryc, on 02 August 2013 - 02:16 AM said:

Correct me if I'm wrong, but I believe it is only positive numerical indices that are in order.

theoriginalbit, on 02 August 2013 - 04:58 AM said:

Symmetryc, on 02 August 2013 - 02:16 AM said:

Correct me if I'm wrong, but I believe it is only positive numerical indices that are in order.

With ipairs negative indexes aren't printed at all and in pairs they are in any random order. This is because negative indexes (and zero) are actually done via a key/value pair, just like when you do `[key] = value`… Thus negative and zero indexes aren't actually indexes and pairs.

Lyqyd, on 03 August 2013 - 04:26 PM said:

Threads merged. Stick to one topic for all questions on a piece of code, please.

You're re-declaring the buttonTable each time you call the button function. Is the problem that you're only seeing one button drawn to the screen? It also looks like only the first character of your text might get drawn (as later iterations of the loop would overwrite the other characters).

Lyqyd, on 03 August 2013 - 04:37 PM said:

Ahh. You've used ipairs. I'm guessing the name variable isn't 1? Try switching to pairs instead.

Lyqyd, on 03 August 2013 - 06:28 PM said:

Stop making new topics for your questions about this code.

You might find it easier to go from xMax to xMin and use a step of -1 so that the coordinates of the rest of the text have already been iterated over by the time you get to the coordinates for the text.

Lyqyd, on 03 August 2013 - 06:52 PM said:

Sure, you phrased it as a more general question, but you were asking because of the issue you were having with this piece of code, weren't you?

function pulse(side, s)
  rs.setOutput(side, true)
  sleep(s)
  rs.setOutput(side, false

function button(name,xMin, xMax, yMin, yMax, text, colorButton, func())

local function passThis()
  print("Hello")
end

local function takeAFunction(func)
  func()
end

takeAFunction(passThis) --#Outputs "Hello"

Lyqyd, on 03 August 2013 - 08:14 PM said:

When you are passing function values, you should put just the variable name. If you include the parentheses, it will call the function and pass the results instead of passing the function itself.

Bubba, on 03 August 2013 - 08:13 PM said:

You can pass a function to a table by simply giving it the variable name, but not calling it. For example:

local function passThis()
  print("Hello")
end

local function takeAFunction(func)
  func()
end

takeAFunction(passThis) --#Outputs "Hello"

You are trying to actually execute the function, which will pass the results rather than the actual function. Just give it the name and it'll work fine.

GamerNebulae, on 04 August 2013 - 04:20 AM said:

But how do I get the function to take variables? The function pulse needs 2 variables: side and s. Where do people fill in those and how can they have separate functions of pulse with different timings or sides?

Bubba, on 04 August 2013 - 07:15 AM said:

GamerNebulae, on 04 August 2013 - 04:20 AM said:

But how do I get the function to take variables? The function pulse needs 2 variables: side and s. Where do people fill in those and how can they have separate functions of pulse with different timings or sides?

You could pass those in as additional arguments to the function. it's a pain, I know.

GamerNebulae, on 04 August 2013 - 09:45 AM said:

Bubba, on 04 August 2013 - 07:15 AM said:

GamerNebulae, on 04 August 2013 - 04:20 AM said:

But how do I get the function to take variables? The function pulse needs 2 variables: side and s. Where do people fill in those and how can they have separate functions of pulse with different timings or sides?

You could pass those in as additional arguments to the function. it's a pain, I know.

What would that look like? I can't really imagine it.

local function passThis(arg)
  print(arg)
end

local function takeFunction(func, arg)
    func(arg)
end
takeFunction(passThis, "hello")

function doThing(takes, three, arguments)
  --stuff here 
end

local funcTable = {}
funcTable[1] = function() return doThing("with", "its", "arguments") end

Lyqyd, on 04 August 2013 - 01:53 PM said:

If the values passed to them don't need to change over time, you can pass in an anonymous function that calls the actual function with the arguments you want:

function doThing(takes, three, arguments)
  --stuff here
end

local funcTable = {}
funcTable[1] = function() return doThing("with", "its", "arguments") end

Notice that the last line declares a new function that just calls the function you actually want to call with the arguments you want it to have.

Lyqyd, on 05 August 2013 - 04:30 PM said:

You're still re-declaring buttonTable itself every time you add a button, so the tables is still going to only contain the last button you create. You need to declare buttonTable only once. As to the error message, you'd need to show us the code you're using with the API as well, not just the API.

os.loadAPI("monitor")
monitor.buttonTable("one", 3, 13, 2, 4, "button", colors.blue, colors.lightBlue)

local buttonTable = {}

function add(name, x, 6)
  buttonTable[name] = {
    x = x,
    y = y,
  }
end

Lyqyd, on 06 August 2013 - 04:03 PM said:

Declare the table above the function.

local buttonTable = {}

function add(name, x, 6)
  buttonTable[name] = {
	x = x,
	y = y,
  }
end

Edit: Also, if you pull this crap a fourth time instead of asking in the topic that already exists for the code you're asking about, I'll put you on a permanent moderator preview.

interactive(table) --# I put the table I saved in here

Lyqyd, on 06 August 2013 - 08:04 PM said:

What do you mean by "recall the table in the loop"? For this code, the table would simply be an upvalue, so it would be accessible by name like any other variable.

os.loadAPI("monitor")
monitor.buttonTable("one", 3, 13, 2, 4, "button", colors.red, colors.lime)
monitor.buttonTable("two", 3, 13, 6, 8, "button", colors.red, colors.lime)
monitor.interactive()

Lyqyd, on 07 August 2013 - 04:12 PM said:

Your declaration for buttonTable itself is still in the function that creates a single button. Why do you think it is a good idea to declare a new table for buttonTable and throw away the old table each time you call that function. You obviously ignored the advice I gave you in my post at the end of the previous page of this topic.