Help with "touchpoint"

Balthamel, on 14 August 2015 - 09:16 AM said:

You want the same button to toggle the redstone on and off?
rs.setOutput("right",(not rs.getOutput("right")))
Or is that not what you want?

local function toggleRedstoneOutputRight()
  rs.setOutput("right",(not rs.getOutput("right")))
end
t:add("left", toggleRedstoneOutputRight , 2, 2, 14, 11, colors.red, colors.lime)

local event, left = t:handleEvents(os.pullEvent())

event, p1, p2, p3, p4, p5 = t:handleEvents(os.pullEvent())

Balthamel, on 14 August 2015 - 09:39 AM said:

Okay I have never used touchAPI before. it looks like there are two ways to use this. either use a function call for what you want the button to do.
For example

local function toggleRedstoneOutputRight()
  rs.setOutput("right",(not rs.getOutput("right")))
end
t:add("left", toggleRedstoneOutputRight , 2, 2, 14, 11, colors.red, colors.lime)

That's what the nil is by the way, it's a bit of code the button should run on being pressed.

ALTERNATIVLY

local event, left = t:handleEvents(os.pullEvent())

should be changed to

event, p1, p2, p3, p4, p5 = t:handleEvents(os.pullEvent())

as described in the api. I'm not sure what values would be assigned to p1 through 5 but I assume one of those values can be used to filter which button was pressed.

reading the examples i realise what you were doing.
p1 is a value provided by the event call! You don't replace p1 with left to toggle the left one you check if the variable p1 == left in your if statement!

Balthamel, on 14 August 2015 - 10:43 AM said:

if event == "button_click" then
if p1 == "left" then

elseif p1 == "right" then

end
end





this line in your first post

local even, left = t:handleEvents(os.pullEvent())

even should be event

left should be p1

in that line of code left is a variable!
this is not what you want!
you want to find out what the string is inside the event button_click
is the string left or right?
so you use
if p1 == "left" then
<do things>


As for free code that does what you ask? this exists in a spoiler on the post you linked to!

if you alter the line in the example script from
t:add("right", nil, 16, 2, 28, 11, colors.red, colors.lime)
and change it to
t:add("back", nil, 16, 2, 28, 11, colors.red, colors.lime)
it should do EXACTLY what you want

os.loadAPI("touchpoint")
local t = touchpoint.new("top")

t:add("left", nil, 2, 2, 16, 19, colors.red, colors.lime)
t:add("left", nil, 21,14, 37, 19, colors.red, colors.lime)

t:draw()

while true do
  local event, left = t:handleEvents(os.pullEvent())
  if event == "buttons_click" then
	t:toggleButton("left")
	rs.setOutput("right", true)
  end
end

t:add("left", nil, 2, 2, 16, 19, colors.red, colors.lime)
t:add("left", nil, 21,14, 37, 19, colors.red, colors.lime)

local event, left = t:handleEvents(os.pullEvent())

t:toggleButton("left")

local event, button = t:hhandleEvents(os.pullEvent())

os.loadAPI("touchpoint")
local t = touchpoint.new("top")

--Notice each of them have a different name
t:add("button1", nil, 2, 2, 10, 3, colors.red, colors.lime)
t:add("button2", nil, 2,4, 10, 5, colors.red, colors.lime)
t:add("button3", nil, 2, 6, 10, 7, colors.red, colors.lime)
t:add("button4", nil, 2,8, 10, 9, colors.red, colors.lime)

t:draw()

while true do
  local event, button = t:handleEvents(os.pullEvent()) --# Grabs the next event that is fired, example being mouse_click, or key_press
  if event == "button_click" then --checking to see if the event was a button_click event opposed to a different type of event.
	if button == "button1" then --# If the button pressed is equal to "button1"
	  print("button1 was pressed")
	elseif button == "button2" then --# if the button pressed is equal to "button2"
	  print("button2 was pressed")
	elseif button == "button3" then --# if the button pressed is equal to "button3"
	  print("button3 was pressed")
	elseif button == "button4" then --# if the button pressed is equal to "button4"
	  print("button4 was pressed")
	end
  end
end

valithor, on 14 August 2015 - 12:26 PM said:

This stands out due to the "" around left. left is a variable, so putting "" around it causes it to treat it as a string rather than a variable.

Balthamel, on 14 August 2015 - 12:56 PM said:

valithor, on 14 August 2015 - 12:26 PM said:

This stands out due to the "" around left. left is a variable, so putting "" around it causes it to treat it as a string rather than a variable.

The button's name is left, instead of passing the button name from the event paramater he is filtering for the paramater and then toggling the button directly. I don't understand why you think he should change that from a string to a variable with a name left!? you either haven't read through all the posts here since this is his latest code
http://pastebin.com/7q2JWAKq
which works just fine with the two fixes i mentioned above
or you have in which case in what world would you tell someone to change the string to a variable name like left when from reading the OP it clearly looks like he's trying to filter the event call using a filter of left and misunderstanding the entire concept of that line and the related comment in the example
–# p1 will be "left" or "right", since those are the button labels

By having him do a quick fix like that you're not helping him understand anything at all and just asking for him to come back here looking for more help every single time!

Balthamel, on 14 August 2015 - 01:00 PM said:

the variable NAME left is a STUPID name the variable left holds string left?! You're not helping him understand you're making it more confusing!

It is better for him to have a good understanding of the language and api than a script that works and no understanding I JUST SAID THAT!

By having him do a quick fix like that you're not helping him understand anything at all and just asking for him to come back here looking for more help every single time!

local even, left = t:handleEvents(os.pullEvent())

t:toggleButton("left")

Balthamel, on 14 August 2015 - 01:00 PM said:

Check the latest code! Telling him he got it wrong again after he's already worked out what was wrong in the OP and (I assume from his sudden silence after my last post) now has functioning code is just in the worst style of know it all condescension and self-aggrandizement that is so prevelent on so many code forums.
By assuming that he has not read through his code, realised he is naming different buttons the same name twice, re-written it in the functioning form you can see in the latest code link you are definately displaying arrogance and the kind of belittlement that I know has driven so many people from learning to code.

valithor, on 14 August 2015 - 01:17 PM said:

I actually started writing all of that post shortly after you wrote your first response, however, I was required to step away from my computer before being able to finish. So no I admit I did not see any post after your first.