RNInputManager uses wrong coordinates

[wolfscaptain]

Line 333:

local x, y = RNFactory.screen.layer:wndToWorld(x, y)

gets the correct world space coordinates for the event, but declares them as local so they aren't actually sent to the correct object on line 336:

local currenTarget = screen:getRNObjectWithHighestLevelOn(x, y);

This is noticeable if you change the origin of the view port, since touch events just aren't triggered correctly for objects.

Removing the local identifier fixes this.

[MattiaFortunati]

Hi wolfscaptain,

I've tested this (also for a stretched view) but if I remove the local identifier nothing is working and touch is not detected.
Maybe the bug for the view port origin translation is somewhere else.