"return true" definitely works as an answer to my original question. Thanks!
Follow-up question for being so helpful...
"return true" is also the cause of my trying to create this workaround.
I am trying to fix an issue with "return true" not stopping a propagation of a touch even to the object (a tableview) below it.
It DOES stop the propagation if I use it before I use other functions, but once another event occurs, "return true" no longer stops propagation.
ANY idea what could possibly be the reason?
Do I need to recreate the function every time to "reactivate" the return true working?
I keep trying and testing different things, using print statement to figure out what's happening.
I've simplified my code down to super basics to see this problem in action:
if event.phase == "ended" then
local function onRowTouch( event )
Here's what happens:
(Scenario 1) When the app starts, I can press the button as many times I like and the "return true" stops it so I get the print statement "BTN TAPPED" without getting the "TAPPED HERE" message. Then I tap on the tableview and get the "TAPPED HERE" message. From this point on, whenever I tap the button, I get both "BTN TAPPED" and "TAPPED HERE" as the touch propagates through both.
(Scenario 2) When the app starts, I press on the tableview first to get the "TAPPED HERE" message. From this point on, whenever I tap the button, I get both "BTN TAPPED" and "TAPPED HERE" as the touch propagates through both.
I've also tried adding a "return true" to the onRowTouch function with no effect.