Problem with event.other during collision

[ldurniat]

Hi @marcodelia1900,

@marcodelia1900

i swapped my local handler in a global handler, and the function is

function onCollision(event) if ( event.phase == "began" ) then print( "began: " .. event.object1.name .. " and " .. event.object2.name ) elseif ( event.phase == "ended" ) then print( "ended: " .. event.object1.name .. " and " .. event.object2.name ) if event.object2.name == "brick" and ball.x + ball.width \* 0.5 \< event.other.x + event.other.width \* 0.5 then xSpeed = -xSpeed elseif event.object2.name == "brick" and ball.x + ball.width \* 0.5 \>= event.other.x + event.other.width \* 0.5 then xSpeed = xSpeed end -- Bounce, Remove if event.object2.name == "brick" then ySpeed = ySpeed \* -1 event.object2:removeSelf() event.object2 = nil end end

still same error, i tried to swap object2 in object1 (obviously i changed ball:addEventListener on Runtime:EventListener)

According to documentation in global handler do not appear variable named event.other. It only exists in local handler.

Object References

Depending on whether collisions are detected locally or globally, references to the objects involved will vary. For more information about these two collision handling methods, see the Collision Detection guide.

 

Local Collision Event   Global Collision Event

 

event.target or self      event.object1

event.other                    event.object2

event.selfElement        event.element1

event.otherElement    event.element2

 

I would use local collision handler for one-many colision detection as @XeduR @Spyric suggested you.

 

Have a nice day:)

 

ldurniat

[marcodelia1900]

@ldurniat

Hi @marcodelia1900,

According to documentation in global handler do not appear variable named event.other. It only exists in local handler.

 

 

Better use local collision handler as @XeduR @Spyric suggested you.

 

Have a nice day:)

 

ldurniat

Hi @Idurniat,

the solution you quoted was the “global” one… the first solution that gave me same problem was the “local” one.

[XeduR]

In local collision handling, you need to pass ( self, event ) into the function. I only said that you seemed to have used global as you hadn’t included both of them. This could be a reason as to why your event.other is nil.

But really, in the future, if you need help with debugging, try uploading a small sample project to the forums that demonstrates your issue. That way people will have a much easier time helping you. At this point it is just about guessing why event.other doesn’t exist within the scope of the function.

[marcodelia1900]

@XeduR

In local collision handling, you need to pass ( self, event ) into the function. I only said that you seemed to have used global as you hadn’t included both of them. This could be a reason as to why your event.other is nil.

But really, in the future, if you need help with debugging, try uploading a small sample project to the forums that demonstrates your issue. That way people will have a much easier time helping you. At this point it is just about guessing why event.other doesn’t exist within the scope of the function.

I can send you my project in private if you want (is really small)

[XeduR]

Sure, you can send it to me via private discussion or at eetu.rantanen@spyric.com.

[XeduR]

Just posting a status update here. I already sent the updated project back to marcodelia1900.

The collision function itself worked fine. The problems were in function scene:show, which was run during both “will” and “did” phases. This meant that all display objects were created twice and the reference to the original ball was lost immediately. Additionally, the bricks also created in a way that each subsequent brick took over the variable’s reference, etc.

So, when the collision function was initially called, it was called because two overlapping balls (one without a reference) were colliding.

There’s a lot left to work on the project, but at least now these major issues are addressed.

Good luck!

[marcodelia1900]

@XeduR

Just posting a status update here. I already sent the updated project back to marcodelia1900.

The collision function itself worked fine. The problems were in function scene:show, which was run during both “will” and “did” phases. This meant that all display objects were created twice and the reference to the original ball was lost immediately. Additionally, the bricks also created in a way that each subsequent brick took over the variable’s reference, etc.

So, when the collision function was initially called, it was called because two overlapping balls (one without a reference) were colliding.

There’s a lot left to work on the project, but at least now these major issues are addressed.

Good luck!

Thanks again bro!