Loop time and renderer:renderPolyline with points widely outside the screen size

LUA addPoint isn't protected against points widely outside the screen, so
the time between the loop calls can be very high on a real transmitter when using
renderer:renderPolyline.

Attached example
when run on emulator, loop time is 21ms
when run on DC-24, Loop time stabilizes near 660ms.

Does lcd.setClipping or renderer:setClipping improve the performance? (fixed some typos btw)

In either case it's an indicator for poor optimization.

The version with lcd.setClipping and ren::setClipping gives on DC-24 850ms (!) loop time in it's .lc form. Doing the setClipping in the tprint once at first run, same behavior.
When using a more reasonable out of screen addPoint(310 * 2, 160 * 2) delay is 20ms with the setClipping.

I found the bug giving very wide y values in my real app on a particular case using a function checkPoint(x, y) called before any addPoint(x,y)
local function checkPoint(x, y)
if (x < 0 or x > app.width) then
print(lFormat(app.Name .. " Bad x=%d",x))
end
if (y < 0 or y > app.height) then
print(lFormat(app.Name .. " Bad y=%d",y))
end
end

l

I have seen the same thing and done the same defense. Have you also noticed that when setting a small clip window on the screen it moves it over by the size of the clip window from the place you specified?

When you set clipping, the X/Y coordinates will be relative to the clipped window/rectangle.

Ah! So the bug is me, not Jeti .. nice