Touchpoint API

--# create a new instance of buttons on the top monitor (assumes API loaded as "touchpoint").
--# you can also not specify a side, and the touchpoint instance will use the current terminal and watch for mouse_click events (ComputerCraft 1.6+ only).
t = touchpoint.new("top")

--# add a button to the instance
t:add("label", function() doStuffButNotRequiredForEventsMode() end, 2, 2, 28, 11, colors.red, colors.lime)
--# coordinates are minX, minY, maxX, maxY.
--# uses red for inactive color and green for active color.

--# draw the set of buttons in the instance
t:draw()

--# catch and handle monitor touch events on buttons to transform them to button_click events
--# (does not require functions when creating buttons, you can pass nil instead)
event, p1, p2, p3, p4, p5 = t:handleEvents(os.pullEvent())

--# or instead handle the button clicks by calling the buttons' functions.
t:run()

--# change a button from inactive color to active or vice versa
t:toggleButton("label")

--# briefly toggle a button's state, then change it back
t:flash("label")

--# change a button's label
t:rename("label", "newLabel")

--# load the touchpoint API
os.loadAPI("touchpoint")

--# intialize a new button set on the top monitor
local t = touchpoint.new("top")

--# add two buttons
t:add("left", nil, 2, 2, 14, 11, colors.red, colors.lime)
t:add("right", nil, 16, 2, 28, 11, colors.red, colors.lime)

--# draw the buttons
t:draw()

while true do
	--# handleEvents will convert monitor_touch events to button_click if it was on a button
	local event, p1 = t:handleEvents(os.pullEvent())
	if event == "button_click" then
		--# p1 will be "left" or "right", since those are the button labels
		--# toggle the button that was clicked.
		t:toggleButton(p1)
		--# and toggle the redstone output on that side.
		rs.setOutput(p1, not rs.getOutput(p1))
	end
end

local buttonName = {
	"		  ",
	" A button ",
	"  label   ",
	"		  ",
	label = "a button"
}

t:add(buttonName, nil, 2, 2, 11, 5, colors.red, colors.lime)

mitchfizz05, on 28 August 2013 - 03:25 AM said:

Poor Direwolf20. Lyqyd's API is taking over.

mitchfizz05, on 28 August 2013 - 03:25 AM said:

Hehe, Lyqyd is the same backwards.

mitchfizz05, on 28 August 2013 - 03:25 AM said:

I do quite like Object Oriented stuff, although I don't really see it anywhere, I think I might look into it a bit.

--Loads the API, straightforward
os.loadAPI("touchpoint")
--establish two "pages" of buttons
local page1 = touchpoint.new("top")
local page2 = touchpoint.new("top")
--one variable to put each page into in order to simplify switching
local t

--Two redstone testing functions
--add toggling where it makes sense
function rsRight()
    page1:toggleButton("Activate Right")
    rs.setOutput("right", not rs.getOutput("right"))
end

function rsLeft()
    page1:toggleButton("Activate Left")
    rs.setOutput("left", not rs.getOutput("left"))
end

--Redstone, switch out
function redMenu()
    t = page2
end

---Main Menu
function mainTable()
    t = page1
end

--set up two pages
do
    page1:add("Redstone", redMenu, 5, 2, 20, 6)
    page1:add("Turtle",function() turtleMenu() end, 25, 2, 40, 6)
    
    page2:add("Activate Left", rsLeft, 5, 12, 20, 16)
    page2:add("Activate Right", rsRight, 25, 12, 40, 16)
    page2:add("Back",mainTable, 15, 18, 25, 22)
end

--Starts with the main Table, then checks for buttons clicked, toggles them, and runs the program it has with my modified t:run2()
mainTable()
while true do
    t:draw()
    -- local event, p1, p2, p3 = os.pullEvent() ---monitor_touch, side, xpos, ypos
    local event, p1 = t:handleEvents(os.pullEvent())   ---button_click, name
    if event == "button_click" then
        --remove toggling and simplify button running
        t.buttonList[p1].func()
    end
end

t:add("Label Text Here", nil, 2, 2, 18, 4, colors.black, colors.black)

function callButton(name)
    if type(t.buttonList[name].func) == "function" then
        t.buttonList[name].func()
    end
end

local labelTable = {
  "    ",
  " 20 ",
  "    ",
  label = "turtleFuel"
}

--# use table labelling to enable total control of button appearance.
page2:add(labelTable, nil, 2, 2, 5, 4, colors.black, colors.black)

--# use rename to change appearance of button without changing label.

local newLabel = {
  "    ",
  " 19 ",
  "    ",
  label = "turtleFuel"
}

--# rename uses the label entry in the table to pick which button to rename, then we give it the new table (with the same label entry to make things easy later)
page2:rename("turtleFuel", newLabel)

rednet.open("right")
while true do
  local id, msg, dis = rednet.receive()
	if msg == "Go Forward" then
	  turtle.forward()
	elseif msg == "Dig" then
	  turtle.dig()
	elseif msg == "Turn Right" then
	  turtle.turnRight()
	elseif msg == "Turn Left" then
	  turtle.turnLeft()
	elseif msg == "Get Fuel Amount" then
	  num = turtle.getFuelLevel()
	  rednet.send(1, ("Fuel Level: "..tostring(num)))
	elseif msg == "Refuel" then
	  if not turtle.refuel() then
		rednet.send(1, "No items to refuel with :(/>/>/>")
	  else
		rednet.send(1, "Refuel Successful!")
		turtle.refuel()
	  end
	else
	  print("ERROR, odd message: ", msg)
	end
end

local testTable = {
  "			",
  " Fuel Level ",
  "			",
  label = "turtleFuel"
}

page3:add(testTable, nil, 5, 20, 21, 24, colors.black, colors.black)

function turtleMenu()
	t = page3
	t:draw()
end

t = page1
t:draw()
while true do
	local event, id, msg, dst = os.pullEvent("rednet_message")
	if id == 1 then
	  page3:rename("turtleFuel", ("Fuel Level: "..msg), true) --msg is the turtle doing rednet.send(1, tostring(turtle.getFuelLevel()))
	end
	local event, p1 = t:handleEvents(os.pullEvent())
	if event == "button_click" then
	  callButton(p1)
	end
end

t = page1
t:draw()
while true do
	--# handleEvents will return any events that it doesn't need to convert, so we can take care of rednet messages here.
	--# We'll put all of the event argument returns in a table for simplicity.
	--# so event is now event[1] and p1 is now event[2].
	local event = {t:handleEvents(os.pullEvent())}
	if event[1] == "button_click" then
		callButton(event[2])
	elseif event[1] == "rednet_message" and event[2] == 1 then
		--# trim string to fit, will only show highest digits.
		local fuelLevel = string.sub(tostring(event[3]), 1, 4)
		--# add padding if necessary
		local fuelLevel = fuelLevel..string.rep(" ", 4 - #fuelLevel)
		--# build entire table for renaming
		local nameTable = {
			"				 ",
			"				 ",
			" Fuel Level: "..fuelLevel,
			"				 ",
			"				 ",
			label = "turtleFuel"
		}
		page3:rename("turtleFuel", nameTable, true)
	end
end

--# the table method requires us to specify every space of every line of the button, and only that many spaces.
--# In other words, it must be the exact size of the button.
local nameTable = {
	"				 ",
	"				 ",
	" Fuel Level	  ",
	"				 ",
	"				 ",
	label = "turtleFuel"
}

local testTable = {
"				", --17 spaces
"Fuel Level", --12 (17-5) spaces (also tried with 17 spaces)
"				", --17 spaces
"				", -- 17 spaces
label = "turtleFuel".
}

page3:add(testTable, nil, 4, 21, 21, 24, colors.black, colors.black) -- I edited your API for my readability so it goes ..., func(), xMin, xMax, yMin, yMax, ...
---Sorry I forgot to mention that before; 21-4 = 17 (hence 17 spaces) and (y)lines 21 to 24 are 4 lines vertically

elseif event[1] =="rednet_message" and event[2] == 3 then
			local fuelLevelUpdate = string.sub(event[3], 1, 5) --changed it to be 5 characters</div>
			local fuelLevelUpdate = fuelLevelUpdate..string.rep(" ", 5 - string.len(fuelLevelUpdate)) --this is a string, not a table anymore so I had to use string.len(), not #
			local nameTable = {
					"			   ", --17 spaces
					"Fuel Level: "..fuelLevelUpdate, --12 spaces (the variables should add 5 more for 17)
					"			   " --17 spaces
					"			   " --17 spaces
					label = "turtleFuel"
			}
			page3:rename("turtleFue", nameTable, true) --This throws the error

for i = self.buttonList[newName].xMin, self.buttonList[newName].xMax do --line 125

if not self.buttonList[newName] then print ("newName = false/nil") end

-- load the touchpoint API
os.loadAPI("touchpoint" )

-- initialize a new button set on the top monitor
local t = touchpoint.new("top")

--ouput rs signal for 10 seconds.
function pulse()
t:toggleButton("door")
shell.run("redpulse", "right", "1", "10")
t:toggleButton("door")
end


-- use coordinates that make a reasonable sized button.
-- do not use parentheses when passing function values, pulse instead of pulse()
t:add("door", pulse, 2, 2, 7, 4, colors.red, colors.lime)
-- coordinates are minX, minY, maxX, maxY.
-- uses red for inactive color and green for active color.

-- since we only want to react to button presses and we have a click function for our button, we can just use this:
t:run()

--# create a new instance of buttons on the top monitor (assumes API loaded as "touchpoint").
t = touchpoint.new("top")
--#If no side is provided makes buttons in terminal instead.

--#All other methods are same as in Standard Varsion

add = function(self, name, func, xMin, yMin, xMax, yMax, inactiveColor, activeColor)

t:add("label", function() doStuffButNotRequiredForEventsMode() end, 2, 2, 28, 11, colors.red, colors.lime)

self, name, func, xMin, yMin, xMax, yMax, inactiveColor, activeColor
"label", function() doStuffButNotRequiredForEventsMode() end, 2, 2, 28, 11, colors.red, colors.lime

adencraft2000, on 10 March 2014 - 04:04 AM said:

-snip-

t:add("label", function() doStuffButNotRequiredForEventsMode() end, 2, 2, 28, 11, colors.red, colors.lime)

t.add(t, "label", function() doStuffButNotRequiredForEventsMode() end, 2, 2, 28, 11, colors.red, colors.lime)

loadup = function()
        shell.run("pastebin", "get", "pFHeia96", "touchpoint")
        os.loadAPI("touchpoint")
        print("Touchpoint API Loaded")
        sleep(1)
        term.clear()
        term.setCursorPos(1,1)
end

loadup()

--make t be local to the whole program, not just the loading function.
local t = touchpoint.new("top")

--rs.getOutput is more reliable for toggling outputs.
function leftAction()
        t:toggleButton("Wither")
        if rs.getOutput("left") == true then
                rs.setOutput("left", false)
        else
                rs.setOutput("left", true)
        end
end

function backAction()
        t:toggleButton("Blaze")
        if rs.getOutput("back") == true then
                rs.setOutput("back", false)
        else
                rs.setOutput("back", true)
        end
end

function rightAction()
        t:toggleButton("Spider")
        if rs.getOutput("right") == true then
                rs.setOutput("right", false)
        else
                rs.setOutput("right", true)
        end
end

--this function must be below the three other functions.
buttonLoads = function()
        t:add("Wither", leftAction, 2, 2, 14, 5, colors.orange, colors.red)
        t:add("Blaze",  backAction, 9, 8, 21, 11, colors.gray, colors.red)
        t:add("Spider", rightAction, 16, 2, 28, 5, colors.blue, colors.red)
        t:draw()
end

buttonLoads()
t:run()

Lyqyd, on 13 March 2014 - 03:19 PM said:

Well, since you have everything declared as globals, it might not matter as much, but it is always a good idea to have functions declared before they are referenced or called. The function that sets up your buttons references your three action functions, one for each button, so it is good to have those functions above it.

--# Find an attached monitor.
local t, x, y
for _, side in ipairs(rs.getSides()) do
  if not t and peripheral.getType(side) == "monitor" then
    t = touchpoint.new(side)
    x, y = peripheral.call(side, "getSize")
  elseif not rednet.isOpen() then
    if peripheral.getType(side) == "modem" then
      rednet.open(side)
    end
  elseif t and rednet.isOpen() then
    break
  end
end

local function action()
  if t.buttonList.Dig then
    --# button currently says Dig.
    t:toggleButton("Dig")
    t:rename("Dig", "Take")
    rednet.send(4, "dig")
  elseif t.buttonList.Take then
    --# button currently says Take.
    t:toggleButton("Take")
    t:rename("Take", "Dig")
    rednet.send(4, "take")
  end
end

t:add("Dig", action, 2, 2, x - 1, y - 1, colors.red, colors.green)

t:run()

local t = touchpoint.new("top")

t:add("NameOfButton", nil, 2, 2, 28, 11, colors.red, colors.lime)

while true do
    local event = {t:handleEvents(os.pullEvent())}
    if event[1] == "button_click" then
        if event[2] == "NameOfButton" then
            if t.buttonList.NameOfButton.active then
                --do stuff when button is active and just got clicked
            else
                --do stuff when button is inactive and just got clicked
            end
        end
    end
end

local t = touchpoint.new("top")

local doAction = function()
    if t.buttonList.NameOfButton.active then
        --do stuff when button is active
    else
        --do stuff when button is inactive
    end
end

t:add("NameOfButton", doAction, 2, 2, 28, 11, colors.red, colors.lime)

t:run()

• I have put a computer down
• Added a screen to the top
• Downloaded the touchpoint script
• Made a script with you example code

t:draw()

sEi, on 27 May 2014 - 10:47 AM said:

Hi Lyqyd

First thanks for the very nice tutorials. They for sure help me a lot getting into CC and LUA.

I have tried your example and it does not work for me.

• I have put a computer down
• Added a screen to the top
• Downloaded the touchpoint script
• Made a script with you example code

When i run the script it draw on the monitor and return to prompt and no error messages.

After testing it exits after/at this code:

t:draw()

The monitor looks like this after program run:
http://dl.dropboxuse...assorted/cc.png

I use MC: 1.7.2 and CC: 1.64pr2

What am i missing?

/sEi

draw = function(self)
	local prevTerm = term.redirect(self.mon)
	term.setTextColor(colors.white)
	term.setBackgroundColor(colors.black)
	term.clear()
	for name, buttonData in pairs(self.buttonList) do
		if buttonData.active then
			term.setBackgroundColor(buttonData.activeColor)
		else
			term.setBackgroundColor(buttonData.inactiveColor)
		end
		for i = buttonData.yMin, buttonData.yMax do
			term.setCursorPos(buttonData.xMin, i)
			term.write(buttonData.label[i - buttonData.yMin + 1])
		end
	end
	term.redirect(prevTerm)	
end

McLeopold, on 27 May 2014 - 10:43 PM said:

….TRUNCATED…

CC 1.6 changed the term api. In the draw function, it ends with "term.restore()" which is no longer valid.

Try this

draw = function(self)
	local prevTerm = term.redirect(self.mon)
	term.setTextColor(colors.white)
	term.setBackgroundColor(colors.black)
	term.clear()
	for name, buttonData in pairs(self.buttonList) do
		if buttonData.active then
			term.setBackgroundColor(buttonData.activeColor)
		else
			term.setBackgroundColor(buttonData.inactiveColor)
		end
		for i = buttonData.yMin, buttonData.yMax do
			term.setCursorPos(buttonData.xMin, i)
			term.write(buttonData.label[i - buttonData.yMin + 1])
		end
	end
	term.redirect(prevTerm)	
end

touchpoint:104: attempt to index ? (a nil value)

func(args)

function() func(args) end

local touch = touchpoint.new("left")
touch:add("Progression", nil, 2, 2, 16, 6, colors.blue, colors.lightblue)
touch:add("Upgrade", upgradeReboot, 56, 13, 69, 17, colors.blue, colors.lightblue)
-- Upgrade System Files and Reboot
function upgradeReboot()
	    touch:toggleButton("Upgrade")
	    --mlapi.tp writes the text to the terminal at location x,y and in specified colours
	    mlapi.tp("Downloading & Upgrading...standby.", 19, 17, colors.white, colors.red)
	    shell.run("update")
	    os.reboot()
end


-- MAINLINE
while true do
	    --mlapi.clear is what I use to clear the monitor screen)
	    mlapi.clear()
	    touch:draw()
	    --tppi.title is the function to draw the logo
	    tppi.title(21, 6)

	    touch:run()
end

Lyqyd, on 16 June 2014 - 03:57 AM said:

Which version of CC are you on? Can you post a screenshot of your setup in-game? Especially whether or not there are any other computers connected to the monitor. Also, I'd just like to confirm that you do have the program running as startup or being run from startup, correct?

START(UP) Program:
term.clear()
local monitor = peripheral.wrap("left")
monitor.setCursorPos(0, 0)
monitor.setTextColor(colors.white)
monitor.setBackgroundColor(colors.black)
monitor.clear()
-- mulambda165 is the actual program.
shell.run("mulambda165")

mckerrnel, on 17 June 2014 - 05:29 AM said:

I tried both, putting the computer in the middle behind the monitor ("back"), and adding sleep(1) at the start up startup script.

It's the weirdest thing. Every OTHER time I run it, it works fine. If It reboots after clicking, it won't let me click anymore. If I break it without clicking and then run it again, it won't let me click. Breaking again and running again works fine.

howdanrocks, on 17 June 2014 - 05:24 AM said:

I downloaded your api and example program to test it, but the buttons come out looking like this:

http://i.imgur.com/uJZ734v.png

Any help? Thanks!

os.loadAPI("touchpoint")

function rsdo()
  rs.setOutput("back", true)
  sleep(1)
  rs.setOutput("back", false)
end

local t = touchpoint.new("top")

t:add("Open!", nil, 1, 1, 18, 5, colors.lime, colors.red)

while true do
  t:draw()
  local event, p1 = t:handleEvents(os.pullEvent())
  if event == "button_click" then
	t:toggleButton(p1)
	t:rename("Open!", "Closed!")
	rsdo()
  end
end

touchpoint:117: attempt to index ? (a nil value)

if p1 == "Open!" then
  t:rename("Open!", "Closed!")
elseif p1 == "Closed!" then
  t:rename("Closed!", "Open!")
end

Lyqyd, on 29 November 2014 - 12:22 AM said:

Well, you never do rename it back to "Open!". The second time you try to rename the "Open!" button to "Closed!", it can't find the button you are trying to rename ("Open!"), because you've already renamed it.

Try swapping the rename line out for this:

if p1 == "Open!" then
  t:rename("Open!", "Closed!")
elseif p1 == "Closed!" then
  t:rename("Closed!", "Open!")
end

local t = touchpoint.new("top")

local t = touchpoint.new("top", "monitor_5")

os.loadAPI("touchpoint")

local page1 = touchpoint.new("top")
local page2 = touchpoint.new("monitor_5")

page1:add("Open!", nil, 1, 1, 5, 5, colors.lime, colors.red)
page2:add("Open!", nil, 1, 1, 5, 5, colors.lime, colors.red)

--toggle buttons on both screens and activate redstone.
function tog()
  page1:toggleButton()
  page2:toggleButton()
  rs.setOutput("back", true)
  sleep(1)							  --to give time for redstone to finish action
  rs.setOutput("back", false)
end

--activate tog() on button click.
while true do
  page1:draw()
  page2:draw()
  local event, p1 = t:handleEvents(os.pullEvent())
  if event == "button click" then
	tog()
	if p1 == "Open!" then  --rename the buttons on click
	  page1:rename("Open!", "Closed!")
	  page2:rename("Open!", "Closed!")
	elseif p1 == "Closed!" then
	  page1:rename("Closed!", "Open!")
	  page2:rename("Closed!", "Open!")
	end
  end
end

local event, p1 = page1:handleEvents(page2:handleEvents(os.pullEvent()))

Lyqyd, on 05 January 2015 - 07:40 PM said:

Yes, an optional duration argument isn't a bad idea.

Edit: I've added this feature. An optional duration argument may now be specified. If it isn't, the default will be used.

function button(e)
if e.label = "1" then
...
t:add("1", button, ...)
t:add("2", button, ...)
t:run()

function button(num)
  if num == 1 then
    --# etc.
  end
end

t:add("1", function() button(1) end, ...)

Lyqyd, on 20 February 2015 - 01:17 AM said:

Well, you could assign your buttons' functions like so:

function button(num)
  if num == 1 then
	--# etc.
  end
end

t:add("1", function() button(1) end, ...)

I hadn't realized I had forgotten to actually put Touchpoint on github, It's there now, and since it is under the MIT license, you are of course free to fork it or do whatever else you like within the limits of the license.

local t = touchpoint.new()

MechTech, on 07 April 2015 - 05:05 PM said:

Hello I am sorry to bother you but I wanted to try your api, but I am not necessarily the best coder in the world :P/>
All I ask of you is to make me a small program with guidelines that will help me understand this API a bit better.
could you write me just a simple program (2 buttons that emit a redstone signal left and right) and help me understand it a little better?
Thanks.

local monitors = {
  "monitor_0",
  "monitor_1",
  "monitor_2",
}

local pages = {}

for i, side in ipairs(monitors) do
  pages[i] = touchpoint.new(side)
end

for i = 1, #pages do
  pages[i]:add("test", nil, 2, 2, 6, 6, colors.red, colors.lime)
end

while true do
  local event = {os.pullEvent()}
  for i = 1, #pages do
    event = {pages[i]:handleEvents(unpack(event))}
  end
  if event[1] == "button_click" then
    -- respond to button clicks here.
  end
end

if event == "button_click" then
  if p1 == "Thermal Kit" then
    --# commands for thermal kit
  elseif p1 == "Thaumic Kit" then
    --# etc.
  end
end

--Loads the API, straightforward
os.loadAPI("touchpoint")
--establish "pages" of buttons
local main = touchpoint.new("top")
local regeln = touchpoint.new("top")
local info = touchpoint.new("top")
local hilfe = touchpoint.new("top")
local allg = touchpoint.new("top")
local chat = touchpoint.new("top")
local stadt = touchpoint.new("top")

--one variable to put each page into in order to simplify switching
local t

--Two redstone testing functions
--add toggling where it makes sense
function main()
    main:toggleButton("Regeln")
    main:toggleButton("Info")
    main:toggleButton("Hilfe")
end

function regeln()
    regeln:toggleButton("Allgemein")
    regeln:toggleButton("Chat")
    regeln:toggleButton("Städte")
end
function info()
    term.clear()
    term.setCurPos(1,1)
    print("")

end

function hilfe()
    term.clear()
    term.setCurPos(1,1)
    print("")

end

function allg()
    term.clear()
    term.setCurPos(1,1)
    print("")

end

function chat()
    term.clear()
    term.setCurPos(1,1)
    print("")

end

function stadt()
    term.clear()
    term.setCurPos(1,1)
    print("")

end

-- Regeln
function regelMenu()
    t = regeln
end

---Main Menu
function mainTable()
    t = main
end

--set up two pages
do


    main:add("Regeln", regelMenu, 5, 2, 20, 6)
    main:add("Info", info, 5, 2, 20, 6)
    main:add("Hilfe", hilfe, 5, 2, 20, 6)


    regeln:add("Allgemein", allg, 5, 2, 20, 6)
    regeln:add("Chat", chat, 5, 2, 20, 6)
    regeln:add("Städte", stadt, 5, 2, 20, 6)
  
  
end

--Starts with the main Table, then checks for buttons clicked, toggles them, and runs the program it has with my modified t:run2()
mainTable()
while true do
    t:draw()
    -- local event, p1, p2, p3 = os.pullEvent() ---monitor_touch, side, xpos, ypos
    local event, p1 = t:handleEvents(os.pullEvent())   ---button_click, name
    if event == "button_click" then
	    --remove toggling and simplify button running
	    t.buttonList[p1].func()
    end
end

Lyqyd, on 14 July 2015 - 07:47 PM said:

You've named both a function and a touchpoint instance "main". You'll need to change one or the other to a different name. All of your other touchpoint instances and functions have the same problem.

Lyqyd, on 15 July 2015 - 05:49 PM said:

That's fine, and you can set it up that way, but you can't use the same name for the touchpoint pages and the functions. You can't have one variable hold two different values at the same time. You could put `page_` at the beginning of the touchpoint page names, for example.

--Loads the API, straightforward
os.loadAPI("touchpoint")
--establish "pages" of buttons
local mainp = touchpoint.new("top")
local regelnp = touchpoint.new("top")
local infop = touchpoint.new("top")
local hilfep = touchpoint.new("top")
local allgp = touchpoint.new("top")
local chatp = touchpoint.new("top")
local stadtp = touchpoint.new("top")
--one variable to put each page into in order to simplify switching
local t
--Two redstone testing functions
--add toggling where it makes sense
function main()
    mainp:toggleButton("Regeln")
    mainp:toggleButton("Info")
    mainp:toggleButton("Hilfe")
end
function regeln()
    regelnp:toggleButton("Allgemein")
    regelnp:toggleButton("Chat")
    regelnp:toggleButton("Städte")
end
function info()
    term.clear()
    term.setCurPos(1,1)
    print("")
end
function hilfe()
    term.clear()
    term.setCurPos(1,1)
    print("")
end
function allg()
    term.clear()
    term.setCurPos(1,1)
    print("")
end
function chat()
    term.clear()
    term.setCurPos(1,1)
    print("")
end
function stadt()
    term.clear()
    term.setCurPos(1,1)
    print("")
end
-- Regeln
function regelMenu()
    t = regeln
end
---Main Menu
function mainTable()
    t = main
end
--set up two pages
do

    mainp:add("Regeln", regelMenu, 2, 2, 10, 11)
    mainp:add("Info", info, 12, 2, 20, 11)
    mainp:add("Hilfe", hilfe, 24, 2, 30, 11)

    regelnp:add("Allgemein", allg, 2, 2, 10, 11)
    regelnp:add("Chat", chat, 12, 2, 20, 11)
    regelnp:add("Städte", stadt, 24, 2, 30, 11)
   
   
end
--Starts with the main Table, then checks for buttons clicked, toggles them, and runs the program it has with my modified t:run2()
main()
while true do
    t:draw()
    -- local event, p1, p2, p3 = os.pullEvent() ---monitor_touch, side, xpos, ypos
    local event, p1 = t:handleEvents(os.pullEvent())   ---button_click, name
    if event == "button_click" then
	    --remove toggling and simplify button running
	    t.buttonList[p1].func()
end
    end

Lyqyd, on 15 July 2015 - 07:50 PM said:

Looks like you'll want to call mainMenu or regelTable before you call t:draw() for the first time. It looks like you haven't put anything into your t variable before you try to use it.

mainTable()

Lyqyd, on 15 July 2015 - 08:01 PM said:

After you call main() and just before the while loop starts, add:

mainTable()

--Loads the API, straightforward
os.loadAPI("touchpoint")
--establish "pages" of buttons
local mainp = touchpoint.new("top")
local regelnp = touchpoint.new("top")
local infop = touchpoint.new("top")
local hilfep = touchpoint.new("top")
local allgp = touchpoint.new("top")
local chatp = touchpoint.new("top")
local stadtp = touchpoint.new("top")
--one variable to put each page into in order to simplify switching
local t
--Two redstone testing functions
--add toggling where it makes sense
function main()
    t = mainp
    mainp:toggleButton("Regeln")
    mainp:toggleButton("Info")
    mainp:toggleButton("Hilfe")
end
function regeln()
    t = regelnp
    regelnp:toggleButton("Allgemein")
    regelnp:toggleButton("Chat")
    regelnp:toggleButton("Städte")
end
function info()
    t = infop
    term.clear()
    print("")
end
function hilfe()
    t = hilfep
    term.clear()
    print("")
end
function allg()
    t = allgp
    term.clear()
    print("")
end
function chat()
    t = chatp
    term.clear()
    print("")
end
function stadt()
    t = stadtp
    term.clear()
    print("")
end

--set up two pages
do

    mainp:add("Regeln", regelMenu, 2, 2, 10, 11)
    mainp:add("Info", info, 12, 2, 20, 11)
    mainp:add("Hilfe", hilfe, 24, 2, 30, 11)

    regelnp:add("Allgemein", allg, 2, 2, 10, 11)
    regelnp:add("Chat", chat, 12, 2, 20, 11)
    regelnp:add("Städte", stadt, 24, 2, 30, 11)
   
   
end
--Starts with the main Table, then checks for buttons clicked, toggles them, and runs the program it has with my modified t:run2()
regeln()
info()
allg()
hilfe()
chat()
stadt()
main()
while true do
    t:draw()
    -- local event, p1, p2, p3 = os.pullEvent() ---monitor_touch, side, xpos, ypos
    local event, p1 = t:handleEvents(os.pullEvent())   ---button_click, name
    if event == "button_click" then
	    --remove toggling and simplify button running
	    t.buttonList[p1].func()
end
    end

Lyqyd, on 15 July 2015 - 09:08 PM said:

You got rid of the regelMenu function, but didn't change which function the button had. The other two buttons on the main menu would just assign t to a blank page, causing the monitor to clear.

Lyqyd, on 16 July 2015 - 07:58 PM said:

If you've fixed that and it still doesn't work like you'd expect, it would be helpful to post your code again and describe in more detail what it's doing or not doing.

--Loads the API, straightforward
os.loadAPI("touchpoint")
--establish "pages" of buttons
local mainp = touchpoint.new("top")
local regelnp = touchpoint.new("top")
local infop = touchpoint.new("top")
local hilfep = touchpoint.new("top")
local allgp = touchpoint.new("top")
local chatp = touchpoint.new("top")
local stadtp = touchpoint.new("top")

--one variable to put each page into in order to simplify switching
local t

--Two redstone testing functions
--add toggling where it makes sense
function main()
    t = mainp
    term.clear()
    mainp:toggleButton("Regeln")
    mainp:toggleButton("Info")
    mainp:toggleButton("Hilfe")
end

function regeln()
    t = regelnp
    term.clear()
    regelnp:toggleButton("Allgemein")
    regelnp:toggleButton("Chat")
    regelnp:toggleButton("Städte")
end
function info()
    t = infop
    term.clear()
    print("")

end

function hilfe()
    t = hilfep
    term.clear()
    print("")

end

function allg()
    t = allgp
    term.clear()
    print("")

end

function chat()
    t = chatp
    term.clear()
    print("")

end

function stadt()
    t = stadtp
    term.clear()
    print("")

end


--set up two pages
do


    mainp:add("Regeln", regelnp, 2, 2, 10, 11)
    mainp:add("Info", infop, 12, 2, 20, 11)
    mainp:add("Hilfe", hilfep, 24, 2, 30, 11)

    regelnp:add("Allgemein", allgp, 2, 2, 10, 11)
    regelnp:add("Chat", chatp, 12, 2, 20, 11)
    regelnp:add("Städte", stadtp, 24, 2, 30, 11)
  
  
end

--Starts with the main Table, then checks for buttons clicked, toggles them, and runs the program it has with my modified t:run2()
regeln()
info()
allg()
hilfe()
chat()
stadt()
main()
while true do
    t:draw()
    -- local event, p1, p2, p3 = os.pullEvent() ---monitor_touch, side, xpos, ypos
    local event, p1 = t:handleEvents(os.pullEvent())   ---button_click, name
    if event == "button_click" then
	    --remove toggling and simplify button running
	    t.buttonList[p1].func()
end
    end

Lyqyd, on 17 July 2015 - 04:46 PM said:

When you're adding the buttons to the pages, you've put in the names of the page instances instead of the names of the functions that change pages.

mainp:add("Regeln", regeln, 2, 2, 10, 11)
    mainp:add("Info", info, 12, 2, 20, 11)
    mainp:add("Hilfe", hilfe, 24, 2, 30, 11)

Lyqyd, on 17 July 2015 - 07:42 PM said:

Yes, that's correct.

--Loads the API, straightforward
os.loadAPI("touchpoint")
--establish "pages" of buttons
local mainp = touchpoint.new("top")
local regelnp = touchpoint.new("top")
local infop = touchpoint.new("top")
local hilfep = touchpoint.new("top")
local allgp = touchpoint.new("top")
local chatp = touchpoint.new("top")
local stadtp = touchpoint.new("top")

--one variable to put each page into in order to simplify switching
local t

--Two redstone testing functions
--add toggling where it makes sense
function main()
    t = mainp
    term.clear()
    mainp:toggleButton("Regeln")
    mainp:toggleButton("Info")
    mainp:toggleButton("Hilfe")
end

function regeln()
    t = regelnp
    term.clear()
    regelnp:toggleButton("Allgemein")
    regelnp:toggleButton("Chat")
    regelnp:toggleButton("Städte")
end
function info()
    t = infop
    term.clear()
    print("")

end

function hilfe()
    t = hilfep
    term.clear()
    print("")

end

function allg()
    t = allgp
    term.clear()
    print("")

end

function chat()
    t = chatp
    term.clear()
    print("")

end

function stadt()
    t = stadtp
    term.clear()
    print("")

end


--set up two pages
do


    mainp:add("Regeln", regeln, 2, 2, 10, 11)
    mainp:add("Info", info, 12, 2, 20, 11)
    mainp:add("Hilfe", hilfe, 24, 2, 30, 11)

    regelnp:add("Allgemein", allg, 2, 2, 10, 11)
    regelnp:add("Chat", chat, 12, 2, 20, 11)
    regelnp:add("Städte", stadt, 24, 2, 30, 11)
  
  
end

--Starts with the main Table, then checks for buttons clicked, toggles them, and runs the program it has with my modified t:run2()
regeln()
info()
allg()
hilfe()
chat()
stadt()
main()
while true do
    t:draw()
    -- local event, p1, p2, p3 = os.pullEvent() ---monitor_touch, side, xpos, ypos
    local event, p1 = t:handleEvents(os.pullEvent())   ---button_click, name
    if event == "button_click" then
	    --remove toggling and simplify button running
	    t.buttonList[p1].func()
end
    end

Lyqyd, on 17 July 2015 - 10:12 PM said:

What is it doing or not doing that makes you say that it "don't work"? It should display your other menu if you hit the "regeln" button. Does it not do that? You haven't configured it to really do much else besides that, since you haven't added buttons to any of the other pages you've created.

OnyxFox, on 11 August 2015 - 01:10 AM said:

Ok so I added a print() command to the code after the pullEvent() so I could see that it is registering the click, however it doesn't register as a "button_click". I'm assuming not because I'm not seeing the button color change or redstone outputs change.

Spoiler

os.loadAPI("touchpoint")
local t = touchpoint.new("top")
t:add("left", nil, 2, 2, 14, 11, colors.red, colors.lime)
t:add("right", nil, 16, 2, 28, 11, colors.red, colors.lime)
t:draw()
while true do
	    local event, p1 = t:handleEvents(os.pullEvent())
	    print("event")
	    if event == "button_click" then
			    t:toggleButton(p1)
			    rs.setOutput(p1, not rs.getOutput(p1))
	    end
end

--# load the touchpoint API
os.loadAPI("touchpoint")
--# intialize a new button set on the top monitor
local t = touchpoint.new("top")
--# add two buttons
t:add("left", nil, 2, 2, 14, 11, colors.red, colors.lime)
t:add("right", nil, 16, 2, 28, 11, colors.red, colors.lime)
--# draw the buttons
t:draw()
while true do
	    --# handleEvents will convert monitor_touch events to button_click if it was on a button
	    local event, p1 = t:handleEvents(os.pullEvent())
	    if event == "button_click" then
			    --# p1 will be "left" or "right", since those are the button labels
			    --# toggle the button that was clicked.
			    t:toggleButton(p1)
			    --# and toggle the redstone output on that side.
			    rs.setOutput(p1, not rs.getOutput(p1))
	    end
end

Lyqyd, on 19 August 2015 - 01:13 AM said:

You are likely experiencing a bug in the latest version of ComputerCraft that causes text to fail to draw on advanced monitors. Changing the size or scale of the monitor sometimes fixes the issue temporarily.

Lyqyd, on 16 August 2013 - 10:58 PM said:

The API can be downloaded from pastebin: pFHeia96

>pastebin get pFHeia96 touchpoint

KingofGamesYami, on 08 September 2015 - 11:57 PM said:

Lyqyd, on 16 August 2013 - 10:58 PM said:

The API can be downloaded from pastebin: pFHeia96

>pastebin get pFHeia96 touchpoint

os.loadAPI("touchpoint")

Lyqyd, on 09 September 2015 - 01:03 AM said:

Once you've downloaded the file (which the above command will do), you just load the API into any programs you want to use it in. That's done by calling os.loadAPI, usually near the beginning of that program:

os.loadAPI("touchpoint")

function allOff()
  for label, button in pairs(t) do
    if button.active then
      button.func()
    end
  end
end

Lyqyd, on 19 September 2015 - 01:07 AM said:

Yep! If all your buttons have functions attached that are called when you press them, and your touchpoint instance is `t`:

function allOff()
  for label, button in pairs(t) do
	if button.active then
	  button.func()
	end
  end
end

The above code also assumes that the buttons' attached functions also toggle the button's state. If your setup is different, please post your code and I can provide a better example.

os.loadAPI("touchpoint")
pos = "front"
m = peripheral.wrap(pos)
t = touchpoint.new(pos)
function openDoor()
  t.toggleButton("Open Launch Bay")
  if rs.getOutput("back") == true then
    rs.setOutput("back", false)
  else
    rs.setOutput("back", true)
  end
end
t:add("Open Launch Bay", nil, 2, 2, 28, 11, colors.red, colors.lime)
t:draw()
while true do
  local event, button = t:handleEvents(os.pullEvent())
  if event == "button_click" then
    if button == "Open Launch Bay" then
	  openDoor()
	  -- t:toggleButton("Open Launch Bay")
    end
  end
end

--# rs.getOutput LEFT.
function leftAction()
t:toggleButton("Pump")
if rs.getOutput("left") == true then
  rs.setOutput("left", false)
else
  rs.setOutput("left", true)
end
end

--# rs.setBundledOutput ORANGE.
function OrangeAction()
t:toggleButton("Pump")
if rs.setBundledOutput("back") == true then
  rs.setBundledOutput("back", 0)
else
  rs.setBundledOutput("back", 2)
end
end

rs.setBundledOutput("back", (colors.test(rs.getBundledOutput("back"), colors.orange) and colors.subtract(rs.getBundledOutput("back"), colors.orange) or colors.combine(rs.getBundledOutput("back"), colors.orange)))

function OrangeAction()
  t:toggleButton("Pump")
  rs.setBundledOutput("back", (colors.test(rs.getBundledOutput("back"), colors.orange) and colors.subtract(rs.getBundledOutput("back"), colors.orange) or colors.combine(rs.getBundledOutput("back"), colors.orange)))
end

Lyqyd, on 14 October 2015 - 05:06 AM said:

Bear in mind that this won't work at all in the latest version of ComputerCraft, as changes to an API entirely broke the colors.subtract function. If you're using 1.74, we'll have to come up with a workaround for that issue.

function OrangeAction()
  t:toggleButton("Pump")
  rs.setBundledOutput("back", rs.getBundledOutput("back") + colors.orange * (colors.test(rs.getBundledOutput("back"), colors.orange) and -1 or 1))
end

Bomb Bloke, on 14 October 2015 - 05:46 AM said:

Lyqyd, on 14 October 2015 - 05:06 AM said:

Bear in mind that this won't work at all in the latest version of ComputerCraft, as changes to an API entirely broke the colors.subtract function. If you're using 1.74, we'll have to come up with a workaround for that issue.

Copy/pasting this snippet up the top of an affected script is one such workaround.

Or:

function OrangeAction()
  t:toggleButton("Pump")
  rs.setBundledOutput("back", rs.getBundledOutput("back") + colors.orange * (colors.test(rs.getBundledOutput("back"), colors.orange) and -1 or 1))
end

--# rs.setBundledOutput ORANGE.
function OrangeAction()
t:toggleButton("Pump")
rs.setBundledOutput("back", (colors.test(rs.getBundledOutput("back"), colors.orange) and colors.subtract(rs.getBundledOutput("back"), colors.orange) or colors.combine(rs.getBundledOutput("back"), colors.orange)))
end

Lyqyd, on 14 October 2015 - 07:57 PM said:

Nothing in there, your button declaration function has colors.slime, which I'm suggesting you change to colors.lime, an actual color.

Lyqyd, on 03 December 2015 - 04:57 AM said:

As mentioned in the documentation in the first post, calling touchpoint.new() with no side specified will return a touchpoint instance that targets the current terminal.

function colours.subtract(cols, ...)
	    for i = 1, #arg do
			    if bit.band(cols, arg[i]) == arg[i] then
					    cols = cols - arg[i]
			    end
	    end
	    return cols
end
colors.subtract = colours.subtract

for label, button in pairs(t.buttonList) do

t.buttonList[p1].func()

Lyqyd, on 28 January 2016 - 12:54 AM said:

Replace the t:run(p1) line with:

 t.buttonList[p1].func() 

Redstoner, on 22 November 2015 - 05:17 AM said:

I Seem to be getting an error that I can't quite figure out. touchpoint:72: attempt to index ? (a nil value) when trying to run my program.
http://pastebin.com/DYETAuDL
It runs the print on line 24 but errors out before the next print call. Any help on this would be appreciated.

Found My issue. Seems :add cannot handle decimals for sizes. I simply had to math.floor() them.

Lyqyd, on 22 February 2016 - 07:53 PM said:

It will be much easier to help if you can post the code you're using.

Lyqyd, on 23 February 2016 - 01:58 AM said:

There are some multiplayer-only click detection bugs, which may be what you're experiencing, unfortunately. If that's the case here (and I suspect that it is), there's nothing anyone but dan200 can do about it.

todo, on 23 February 2016 - 02:08 PM said:

Lyqyd, on 23 February 2016 - 01:58 AM said:

There are some multiplayer-only click detection bugs, which may be what you're experiencing, unfortunately. If that's the case here (and I suspect that it is), there's nothing anyone but dan200 can do about it.

Alright, I guess I'll just try and see if I can make a workaround or something.
Thanks again =)

Lupus590, on 23 February 2016 - 02:34 PM said:

todo, on 23 February 2016 - 02:08 PM said:

Lyqyd, on 23 February 2016 - 01:58 AM said:

There are some multiplayer-only click detection bugs, which may be what you're experiencing, unfortunately. If that's the case here (and I suspect that it is), there's nothing anyone but dan200 can do about it.

Alright, I guess I'll just try and see if I can make a workaround or something.
Thanks again =)

making the buttons bigger is the easiest way

os.loadAPI("touchpoint")

local t = touchpoint.new("top")

--# add two buttons
t:add("left", left, 2, 2, 9, 4, colors.gray, colors.lime)
t:add("right", right, 16, 2, 28, 11, colors.red, colors.lime)

--# draw the buttons
t:draw()

function right()
  t:flash("right")
  print("right")
  rs.setAnalogOutput("right", 14)
  sleep(3)
  rs.setAnalogOutput("right",0)
end

function left()
  t:flash("left")
  print("left")
  rs.setAnalogOutput("left",15)
  sleep(3)
  rs.setAnalogOutput("left",0)
end

function callButton(name)
   if t.buttonList[name].func ~= nil then
	 t.buttonList[name].func()
   end
end

while true do
		--# handleEvents will convert monitor_touch events to button_click if it was on a button
		local event, p1 = t:handleEvents(os.pullEvent())
		if event == "button_click" then
				 --t:run(p1)
				--callButton(p1)
				if p1 == "right" then right()
				elseif p1 == "left" then left() end
			  
		end
end

t:run()

if event == "button_click" then
  if t.buttonList[p1].func then --# if this button has a function associated with it
    t.buttonList[p1].func() --# call the function
  else
    --# handling for buttons without functions attached, if any
    --# you can remove this else clause if all of your buttons have functions
  end
end

while true do
  local event = {t:handleEvents(os.pullEvent())}
  if event[1] == "button_click" then
    --# handle button clicks here
  elseif event[2] == "rednet_message" then
    --# handle rednet messages here
  end
end

while true do
    t:draw()
    local event = {t:handleEvents(os.pullEvent())}
    
    if event[1] == "button_click" then
        --# use the event information in the event table to get the button name.
        t.buttonList[event[2]]func()
        
    elseif event[1] == "rednet_message" then
        --# event[2] is id, event[3] is message, event[4] is protocol.
        --# no need for a rednet.receive(), you can use the rednet_message events directly.
    
        if event[4] == fuelId then
            fuel()
        elseif event[4] == oilId then
            oil()
        end
    end
end

touchpoint:13: vm error:
java.lang.NegativeArraySizeException

os.loadAPI("touchpoint")

local t = touchpoint.new("left")

local codeArray = {}

local location = 1

function addNum(n)
	codeArray[location] = n
	location = location + 1
end

function clear()
	for i=1, 5 do
		codeArray[1] = nil
	end
end

function enter(c)
	if c[1] == 0 then
		if c[2] == 1 then
			if c[3] == 4 then
				if c[4] == 7 then
					if c[5] == 0 then
						rs.setOutput("front", true)
						sleep(3)
						rs.setOutput("front", false)
					end
				end
			end
		end
	end
	clear()
end

clear()

t:add("Code:", 1, 1, 7, 1, colors.black, colors.black)
t:add("1", 3, 2, 3, 2)
t:add("2", 4, 2, 4, 2)
t:add("3", 5, 2, 5, 2)
t:add("4", 3, 3, 3, 3)
t:add("5", 4, 3, 4, 3)
t:add("6", 5, 3, 5, 3)
t:add("7", 3, 4, 3, 4)
t:add("8", 4, 4, 4, 4)
t:add("9", 5, 4, 5, 4)
t:add("C", 3, 5, 3, 5)
t:add("0", 4, 5, 4, 5)
t:add("X", 5, 5, 5, 5)

t:draw()

while true do
	local event, p1 = t:handleEvents(os.pullEvent())
	if event == "button_click" then
		if p1 == "1" then
			t:flash("1")
			addNum(1)
		elseif p1 == "2" then
			t:flash("2")
			addNum(2)
		elseif p1 == "3" then
			t:flash("3")
			addNum(3)
		elseif p1 == "4" then
			t:flash("4")
			addNum(4)
		elseif p1 == "5" then
			t:flash("5")
			addNum(5)
		elseif p1 == "6" then
			t:flash("6")
			addNum(6)
		elseif p1 == "7" then
			t:flash("7")
			addNum(7)
		elseif p1 == "8" then
			t:flash("8")
			addNum(2)
		elseif p1 == "8" then
			t:flash("2")
			addNum(2)
		elseif p1 == "9" then
			t:flash("9")
			addNum(9)
		elseif p1 == "0" then
			t:flash("0")
			addNum(0)
		elseif p1 == "C" then
			t:flash("C")
			clear()
		elseif p1 == "X" then
			t:flash("X")
			enter(codeArray)
		end
	end
end

if t.buttonList["8"].active then

function setActivity(instance, name, active)
  instance.buttonList[name].active = active
  instance:draw()
end

.temp:100: attempt to index ? (a function value)

os.loadAPI("touchpoint")
do
local main = touchpoint.new("top")
local rocket = touchpoint.new("top")
local security = touchpoint.new("top")
local facility = touchpoint.new("top")
local lockdown = touchpoint.new("top")
local login = touchpoint.new("top")
local t = login
local currentUser = "system"
local currentUserLabel = {
" " .. currentUser,
label = userLabel
}
local lockDownLabel = {
  "	 ",
" (/) ",
"	 ",
label = "lockdownButton"
}
end
do
function login()
  rs.setBundledOutput("right", 6)
  sleep(3)
  if rs.testBundledInput("right", colors.white) then
   currentUser = "cox_11"
  end
  rs.setBundledOutput("right", 0)
  main()
end
function exitToLogin()
  t = login
  currentUser = "system"
end
function rocket()
  t = rocket
end
function security()
  if currentUser == "cox_11" then
   t = security
  else
   print(currentUser + " has attempted to access the Security Menu")
  end
end
function facility()
  t = facility
end
function main()
  t = main
end
function lockdown()
  t = lockdown
end
function lockdownStop()
  if currentUser == nil then
   exitToLogin()
  else
   main()
  end
end

function mainDoorLock()
end

function turretToggle()
end

function loadItems()
end

function loadFuel()
end

function mainHatchToggle()
end

function launchRocket()
end

function lockdownStop()
  login()
end

function reactor()
end
end
do
  do
	login:add("Login ->", login(), 21, 12, 30, 14) --This line is line 100!!!!!!! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
	login:add("Lockdown ->", nil, 2, 2, 14, 11, colors.black)
  end
  do
	main:add("Rocket Control", rocket(), 2, 2, 21, 6)
	main:add("Security Control", security(), 2, 8, 21, 12)
	main:add("Facility Control", facility(), 2, 14, 21, 18)
	main:add("Logout", exitToLogin(), 40, 2, 47 2)
  main:add("Current User:", nil, 2, 23, 21, 23, colors.black)
  main:add(currentUserLabel, nil, 7 ,23, 21, 23)
  end
  do
	security:add("Lock Main Door", mainDoorLock(), 2, 2, 21, 6)
	security:add("Toggle Turrets", turretToggle(), 2, 8, 21, 12)
  end
  do
	rocket:add("Load Items", loadItems(), 2, 2, 21, 6)
	rocket:add("Load Fuel", loadFuel(), 2, 8, 21, 12)
	rocket:add("Toggle Main Hatch", mainHatchToggle(), 2, 14, 21, 18)
	rocket:add("LAUNCH", launchRocket(), 2, 20, 21, 26)
  end
  do
	facility:add("Reactor", reactor(), 2, 2, 14, 11)
  end
  do
	lockdown:add("Disable Lockdown", lockdownStop(), 2, 2, 11, 14)
  end
end
function callButton(name)
	if type(t.buttonList[name].func) == "function" then
		t.buttonList[name].func()
	end
end
while true do
  t:add(lockDownLabel, lockdown(), 44, 23, 49, 26)
  if not (t == main) then
	t:add("Back", main(), 40, 2, 47, 2)
end
  t:draw()
  local event, p1 = t:handleEvents(os.pullEvent())
  if event == "button_click" then
	callButton(p1)
  end
end

local login = touchpoint.new("top")

function login()

--# load the touchpoint API
os.loadAPI("touchpoint")
--# intialize a new button set on the top monitor
local t = touchpoint.new("left")
function Gate()
	    t:flash("Gate")
	    rednet.broadcast("gate")
end
function red()
	    t:flash("red")
	    rednet.broadcast("d1")
end
function yellow()
	    t:flash("yellow")
	    rednet.broadcast("d2")
end
function blue()
	    t:flash("blue")
	    rednet.broadcast("d3")
end
function king()
	    t:flash("king")
end
--# add two buttons
t:add("Gate", Gate, 1, 1, 18, 4, colors.green, colors.orange)
t:add("Door Red", red, 1, 5, 18, 8, colors.red, colors.orange)
t:add("Door Yellow", yellow, 1, 9, 18, 12, colors.yellow, colors.orange)
t:add("Door Blue", blue, 1, 13, 18, 16, colors.blue, colors.orange)
t:add("King's Arena", king, 1, 17, 18, 19, colors.purple, colors.purple)
--# draw the buttons
t:draw()

while true do
  t:draw()
  local event, p1 = t:handleEvents(os.pullEvent())
  if event == "button_click" then
    if p1 == "FARM_MAP" then
      shell.run("FarmMap")
    end
  end
end

Androthia, on 08 November 2016 - 08:29 PM said:

-snip-

Bomb Bloke, on 07 November 2016 - 09:57 AM said:

What I suspect is that, when you're done with them, you're having your child scripts (FarmMap etc) attempt to re-call the menu script. You've then got an instance of the original menu waiting for eg FarmMap to complete, which is in turn waiting for the new menu instance it spawned to complete, and so on… Better to just have the child scripts return / error / hit EOF / whatever instead, allowing the original menu to carry on each time every time you want to go back to it.

Androthia, on 09 November 2016 - 09:19 PM said:

Ok, Lyqyd….and with Touchpoint, would there be an easier way to switch from screen to screen? If so….could you point me in the direction for a tutorial on how to do such a thing instead of calling a different program for each different gui?

Thanks

--# using comments as I'm too sleepy to actually look up the API functions I should be calling
local function exampleMenu()
  --# create new terminal object with the window API (or some other API)
  --# redirect the terminal to this new window (remember to store the returned value, this was the old terminal object)
  --# create a new touchpoint instance, this will 'bind' itself to this terminal object.
  --# draw buttons

  local exit = false
  while not exit do --# event loop
	local event = {os.pullEvent()}
	--# process event, handle buttons, ect.
  
	--# eventually the back button will be pressed, which only sets exit to true, ending the loop and returning the function
  end
  --# cleanup bit, restore the current terminal to the one which was stored at the start of this function
end

standal, on 13 January 2017 - 01:16 PM said:

hello, I would like to ask for your help I done something wrong and I can not find where to but does not display the contents of the chest
I thanked him for his help when someone tuna
http://raw.githubuse...ter/Spawner.lua

event, message, p1 =  t:handleEvents(os.pullEvent())
If event == "button_click" then
  print(p1)
elseif event == "modem_message" then
  print(message)
end

local event, param1, param2, param3, param4, param5 = t:handleEvents(os.pullEvent())
if event == "button_click" then
  print(param1) --# the name of the button clicked
elseif event == "modem_message" then
  print(param4) --# the message that arrived
end

Lyqyd, on 29 March 2017 - 04:16 AM said:

You'd want to use less event-specific names for the event parameter variables. I usually just chuck them all in a table and index out what I need, but if you prefer the list:

local event, param1, param2, param3, param4, param5 = t:handleEvents(os.pullEvent())
if event == "button_click" then
print(param1) --# the name of the button clicked
elseif event == "modem_message" then
print(param4) --# the message that arrived
end

But you're definitely on the right track! The ability to handle multiple types of events is exactly what the handleEvents function in Touchpoint was built for.

 t:handleEvents(os.pullEvent())

While true do
  Local event, param1, param2, param3, param 4, param5 = t:handleEvents(os.pullEvent())
  If event == "button_click" then 
    Local 1 = param1 --# This can be changed to store inputs as a table, if it's more efficient or 'better'
    	--# I don't know what to put here

local buttonStatus = false

local function buttonFunction()
  if buttonStatus then
    -- Button is set, toggle it off and send one message.

  else
    -- Button is not set, toggle it on and send the other message.

  end

  buttonStatus = not buttonStatus  -- Invert the boolean.
end

loginPage:add("Hello", function() display(mainMenu) end, etc...

loginPage:add("Hello", function() return display(mainMenu) end, 21, 9, 30 ,11)

HamishWHC, on 13 April 2017 - 03:10 AM said:

How do I put images in it with paintutils or another way if needed?

brainytwoo, on 24 April 2017 - 07:59 PM said:

Is there a way to have more then 1 button with the same name on the same page at the same time?
for instance:
|-100| |-10| |-5| |num 1| |+5| |+10| |+100|
|-100| |-10| |-5| |num 2| |+5| |+10| |+100|

brainytwoo, on 24 April 2017 - 08:25 PM said:

I just realized that you don't need to have touchpoint handle the events, do you?
if not, I could simply add an if statement checking weather the touch is on the top or bottom of the screen and toggle the button accordingly.
If there is someone that has done anything like this before and has a better solution, please let me know.
Thanks and have a great day.

os.loadAPI("buttonAPI")
t=buttonAPI.new()
local reactor100 = {
	    " -100 ",
	    label = "r-100"
}
local reactor10 = {
	    "  -10 ",
	    label = "r-10"
}
local reactor5 = {
	    "  -5  ",
	    label = "r-5"
}
local reactorr5 = {
	    "  +5  ",
	    label = "r+5"
}
local reactorr10 = {
	    "  +10 ",
	    label = "r+10"
}
local reactorr100 = {
	    " +100 ",
	    label = "r+100"
}
t:add(reactor100, nil, 1, 5, 6, 5, colors.red, colors.lime)
t:add(reactor10, nil, 8, 5, 13, 5, colors.red, colors.lime)
t:add(reactor5, nil, 15, 5, 20, 5, colors.red, colors.lime)
t:add(reactorr5, nil, 31, 5, 36, 5, colors.red, colors.lime)
t:add(reactorr10, nil, 38, 5, 43, 5, colors.red, colors.lime)
t:add(reactorr100, nil, 45, 5, 50, 5, colors.red, colors.lime)
t:draw()
while true do
  local event, p1 = t:handleEvents(os.pullEvent())
  if event == "button_click" then
    t:toggleButton(p1)
  end
end

if currentPage.buttonList[p1].func then
  currentPage.buttonList[p1].func()
end

Lyqyd, on 26 April 2017 - 01:58 AM said:

You can't mix :run() and :handleEvents(). Instead of the run call, try:

if currentPage.buttonList[p1].func then
  currentPage.buttonList[p1].func()
end

Lyqyd, on 16 August 2013 - 10:58 PM said:

-snip-
A note: One can also fully specify the text characters of the button by providing a table for the label. The table should contain exactly the text of the button, in numerical indices, top to bottom. Each index should be as long as the button is wide. A label entry should be present in the table, which should be a single string to be used as the name of the button. For example:

local buttonName = {
	"		  ",
	" A button ",
	"  label   ",
	"		  ",
	label = "a button"
}

t:add(buttonName, nil, 2, 2, 11, 5, colors.red, colors.lime)

--# load the touchpoint API
os.loadAPI("touchpoint")
local width,height = term.getSize()
local buttonWidth = math.floor((width-2)*0.5)
--local buttonWidth = width
local buttonHeight = 1
--# intialize a new button set on the top monitor
local topBar = touchpoint.new()
--# add two buttons
topBar:add("goto", nil, 1, 1, buttonWidth, buttonHeight)
topBar:add(" ",nil,buttonWidth,1,3,buttonHeight,colors.white,colors.red)
topBar:add("come", nil, buttonWidth+1, 2, buttonWidth, buttonHeight)
--# draw the buttons
topBar:draw()
while true do 
	    --# handleEvents will convert monitor_touch events to button_click if it was on a button
	    local event, p1 = topBar:handleEvents(os.pullEvent())
	    if event == "button_click" then
			    --# p1 will be "left" or "right", since those are the button labels
			    --# toggle the button that was clicked.
			    topBar:toggleButton(p1)
			    --# and toggle the redstone output on that side.
			    --rs.setOutput(p1, not rs.getOutput(p1))
	    end
end

name, [func], xMin, yMin, xMax, yMax [, inactiveColor] [, activeColor] [, inactiveText] [, activeText]

touchpoint:96: attempt to index ? (a nil value)

if self.clickMap[i][j] ~= nil then

for i = xMin, xMax do
for j = yMin, yMax do
print("i: ", i, " j: ", j)
if self.clickMap[i][j] ~= nil then
--undo changes

go-monitor:14: attempt to concatenate string and nil

xMin: 8 xMax: 28
yMin: 1 yMax: 3
touchpoint:98: attempt to index ? (a nil value)

17
3
18
1
18
2
18
3
19
1
touchpoint:103: attempt to index ? (a nil value)

local x, y = buttonInstance.mon.getSize()

local x, y = buttonInstance.mon.getSize()

local t = touchpoint.new("monitor_4")
t.mon.setTextScale(.5)

Patistar, on 02 January 2018 - 07:12 PM said:

Hello,

I use a slightly modified version of your api which is extended by a clear and getState function. My version can be found here: https://pastebin.com/4eCwR0Dk

When the server restarts I get the following error message on all computers running the touchpoint api:

touchpoint:96: attempt to index ? (a nil value)

after a manual computer restart everything is fine. But the process of starting every single computer manually is annoying.

kain184, on 05 February 2018 - 05:35 AM said:

how can i access data in the button table inside the api. i want to test if one of the buttons is on or not.

t.buttonList

if t.buttonList[label].active then