This example adds setUserData/getUserData capabilities to an Image object and demonstrates them. It also shows the count of elements in the objectData table. When pressing the space bar, the image is deleted and garbage collection is run immediately to show how the weak element is deleted. For some ...

If you have a strong reference somewhere else in the code - the weak ref will never be collected. That's the point. With this method, the user data will be associated to the object for as long as the object is alive. If you destroy the object, the associated data will be automatically destroyed as ...

You will have a strong reference to the body somewhere, and you can access the associated data using the body as the key to the weak table. The weak key means that the element will be automatically removed from the table when the body disappears. What raidho and I are trying to say is that setUserDa...

That's indeed the approach that 4vZEROv posted in the previous page (except 'inherit()' is called 'extend()' in 4vZEROv's version).

I don't use PUSH or SUIT either, but I think this function may help: https://suit.readthedocs.io/en/latest/core.html#mouse-input No idea how it's used, though. The docs are quite terse on that. If it doesn't help, maybe overriding getMousePosition works (https://suit.readthedocs.io/en/latest/core.ht...

But then you have to modify the table every time a body is created or destroyed. As for creation, in the other method you have to setUserData anyway, so there's no significant advantage - both methods require an action at creation time. As for destruction, weak tables take care of that automaticall...

Thanks for the quick replies using npcbutton[i][o].click = function(self, x, y) (wasnt using self before,oversight) returns the same error: Gspot.lua:380: attempt to index local 'element' (a nil value) --with a traceback to this line: gui:rem(npcbutton[playertargetid][playertargetnpc]) Line 380 jus...

Something very similar happened to someone very recently. What happens is that when checking the collision with the first object, 'hero.observes' is made true, but the loop continues and when checking the collision with the second object, 'hero.observes' is overwritten and set to false. You need to ...

I create my projectile like this: ... local bulletDx = visor.speed*2 * math.cos(angle) -- destination X local bulletDy = visor.speed*2 * math.sin(angle) -- destination Y ... Wouldn't it suffice to randomize the angle a bit? Something like this: angle = angle + love.math.random() * bulletSpreadAngle...

Is there another way to set functions for each instance of button other than using a colon ? For normal functions you use dots, not colons. You use a colon just before the last element when you want to call a method in an instance of an object, because that passes the instance as an implicit parame...