Question about addEventListener

Solar2D General Questions/Discussion
#1

Hello,

One question : (the other is solved lol thx)

I so loved to have the inner code of the function “addEventListener”.

Is it possible to have an history link about this function ?

I think it’s firstly defined on stage.currentStage._class table and when we create a display object, an index table is automatically given to the metatable’s object with a key value look’s like "index.addEventListener=function(self,event)… "

Is it correct ? A clue pleased lol .

Thanks.

#2

  1.  when using a table as a listener, the name of the method must exactly match that of the event, “tab” ~= “tap”.  (when using a function as a listener, you may use any legal name, or even anonymous) and the “expectation” is that you’d be using the same object, fe:

    circle.tap = function(self,event) print(1) end circle:addEventListener(“tap”)

  2.  i can’t follow your use of “history link” here, so no idea what you’re asking, but…  all display objects descend from EventDispatcher which provides the add/removeEventListener methods.  if the passed listener is a table it attempts to dispatch as object[“eventName”](object, event) (there are at least three syntactically equivalent ways of writing that call) but none of that really matters, because all that actual dispatching happens internally, out of your control.

#3

Just corrected lol thanks.

I ask in fact of having the internal description code of the addEventListener function.

#4

Why are you using a proxy to do the work?
 
Just put the listener on the object and it will self-clean when you delete the object.
 
 
Here is a basic random example showing some good practices.

-- One function, used by multiple objects local function onTap( self, event ) print( self.name ) display.remove( self ) -- safer than calling obj:removeSelf() end local circle = display.newCircle( 0, 100, 30 ) circle.name = "Bill" -- Store any values you want as fields on the object. circle.tap = onTap -- Assign function reference to field with same name as event, then... circle:addEventListener( "tap" ) -- No need to pass obj, it is implied. -- Make another 'circle'... local circle = display.newCircle( 100, 100, 30 ) circle.name = "Bob" circle.tap = tap circle:addEventListener( "tap" ) -- And another... local circle = display.newCircle( 200, 100, 30 ) circle.name = "Sue" circle.tap = tap circle:addEventListener( "tap" )
#5

ok for that answer.

Why do you tell proxy ? I don’t understand.

Do you have the internal description code of the addEventListener function ?

Thanks

#6

Why did you change original post to a new question?

Never never never … change your original post to ask a new question.

I simply won’t help you in the future if you do this again.  The reasons for having a forum are:

  1. Get help when you are stuck.

  2. Keep a record of the conversation so others with similar questions can learn from the conversation in the future.

If you want to continue the discussion, add the new details at the end of the post, as long as it is closely related to the original question.

However, starting a whole new question at the end of a post bad practice.  This is not an email thread.  

Generally the best practice is ONE question per thread.  i.e. Make new posts for new questions.  This is most useful for future readers.  If you’re extra awesome you can go back and link the threads to each other for future readers.

( Update: This may seem like a total freakout, but I put real effort into answering forums questions and It is a super-pet-peeve of mine to see that effort wasted. )

Your original text was:

Hello,

 

2 things :

 

First the “table listener” don’t work with a “tap” detection.

local t={}
t.tab=function() print(1) end

local cercle=display.newCircle(0,0,30)
cercle:addEventListener(“tap”,t)
– Don’t work !

Second, I so loved to have the inner code of the function “addEventListener”.

Is it possible to have an history link about this function ?

 

I think it’s firstly defined on stage.currentStage._class table and when we create a display object, an index table is automatically given to the metatable’s object with a key value look’s like "index.addEventListener=function(self,event)… "

 

 

Is it correct ? A clue pleased lol

 

Thanks.

 

Proxy
In your original question’s code snippet, you had this:

local t={} t.tab=function() print(1) end local cercle=display.newCircle(0,0,30) cercle:addEventListener("tap",t)

In this code, you are using the the table ‘t’ as a proxy to catch event.  Or at least you were trying to.  This is a valid practice, but is is advanced and most people do not need to do it in their apps or games.

Do you have the internal description code of the addEventListener function ?

No idea what this means.  Please elaborate on ‘internal description’

#7

lol sorry for the changes, i think it was good like that.

For the second question, I speak about the full code behind the addEventListener function, which means :

local function addEventListener(self,event) ... the code inside, i hope to have this ... end

Thanks :smiley:

#8

I simple don’t understand what you mean.

Maybe you should explain this by giving me a concrete example of what you hope to achieve.  

All I can say is.  In the example I’ve given:

  • self is a reference to the object that is being tapped (same as the object the listener is ‘attached’ to).
  • event is the standard tap event table.
  • In Corona apps, you can neither access the original script (it gets compiled to bytecode) during execution, nor can you modify it.
  • If you need a reference to the function itself (no idea what you would use this for), based on my code, you can find it at self.tap
#9

Edited and improved answer above.

#10

My question is to know if it’s possible to have the code that create the addEventListener method.

For example, 

local cercle=display.newCircle(0,0,30) cercle:addEventListener("touch",function(event) end)

In this example, the object “cercle” call the method “addEventListener” and then I write the event name “touch” and the listener function.

But what is the code executed inside that method ??

I imagine its begin like that :

local function addEventListener(self,eventName,listener) ... the code inside is what I want end
#11

I think this gives me the answer.

So it’s impossible to have the original code build inside ?

#12

Correct, It is not possible to access the plain text lua code.

You still haven’t said WHY you want to do this.  

If you could elaborate on the why, I or others might have suggestions that help you achieve your true end goal.

Tip: Corona does (contrary to popular belief) support loadString, but you are NOT (according to the Apple guidelines) allowed to use it in iOS apps.

#13

what a strange thread this is… I do not see the point in it at all!  Very confusing…

Forum etiquette totally thrown out of the window, kicked down the road and booted into the river!

#14

thread or threat?

#15

thread… its late on Sunday

#16

If all you’re interested in is how addEventListener works in general, here’s one implementation:

https://github.com/daveyang/EventDispatcher/blob/master/EventDispatcher.lua

#17

Just to know how it work and how them made it.

 

ok thanks qwidave that’s what I wanted !

#18

  1.  when using a table as a listener, the name of the method must exactly match that of the event, “tab” ~= “tap”.  (when using a function as a listener, you may use any legal name, or even anonymous) and the “expectation” is that you’d be using the same object, fe:

    circle.tap = function(self,event) print(1) end circle:addEventListener(“tap”)

  2.  i can’t follow your use of “history link” here, so no idea what you’re asking, but…  all display objects descend from EventDispatcher which provides the add/removeEventListener methods.  if the passed listener is a table it attempts to dispatch as object[“eventName”](object, event) (there are at least three syntactically equivalent ways of writing that call) but none of that really matters, because all that actual dispatching happens internally, out of your control.

#19

Just corrected lol thanks.

I ask in fact of having the internal description code of the addEventListener function.

#20

Why are you using a proxy to do the work?
 
Just put the listener on the object and it will self-clean when you delete the object.
 
 
Here is a basic random example showing some good practices.

-- One function, used by multiple objects local function onTap( self, event ) print( self.name ) display.remove( self ) -- safer than calling obj:removeSelf() end local circle = display.newCircle( 0, 100, 30 ) circle.name = "Bill" -- Store any values you want as fields on the object. circle.tap = onTap -- Assign function reference to field with same name as event, then... circle:addEventListener( "tap" ) -- No need to pass obj, it is implied. -- Make another 'circle'... local circle = display.newCircle( 100, 100, 30 ) circle.name = "Bob" circle.tap = tap circle:addEventListener( "tap" ) -- And another... local circle = display.newCircle( 200, 100, 30 ) circle.name = "Sue" circle.tap = tap circle:addEventListener( "tap" )