Then I think the challenge is set. Sorunome, make us 'more or less' in brainf*ck, NOW!

nope, i could toggle the boolean each time you press though, but that's kinda unhandy, isn't it?

edit: you can't detect a keyUp in lua

yeah, sure, otherwise it wouldn't be fun anymore. I only realised something. The nspire has no quality key-repeat. So whenyou press the arrow key it takes about a second before it gets recognized as a continuous pressing, and even once it started, it only calls on.arrowKey() 5 times per seconds (+-), so i would have to find a way to handle this.. and other keys don't have keyrepeat at all (except for [tab] i think)

Oh man this is sooo awesome, I'm quite sure that'll be it, thanks for that tip sorunome

Indeed, i'm sure it will but it's so awesome, isn't it?

Very nice, but how come it is so incredibly slow in the 'beautiful' mode?

does math.atan() give the same on calc ?

I changed the math.atan2(yDif, xDif) by math.atan(yDif/xDif) and that gives the same results as atan2 on pc and calc, so again different values.

Also, calling the nspire's math engine gives the same (just for testing, it's way too slow to use for real while in calculations, I guess) ?

if I do tan-1(150/20) I get the same result on calc and pc (1.44) when in radian, same for degrees, but then 82.4, which is correct.
I also changed the settings to both radian and degrees of both the pc and the calc, but that does not seem to influence anything (just to make sure).

I guess i've tried all possible solutions:
local tan = math.atan2(yDif, xDif)
local tan = math.atan(yDif/xDif)
local tan = tonumber(math.eval(""..math.atan2(yDif,xDif)))
local tan = tonumber(math.eval(""..math.atan(yDif/xDif)))
it lways keeps returning 1.44 on pc (correct) and 0.68 on calc (wrong).

edit: I'll redo math.Eval, now it just returns a number of course, since the calculation already happens in lua, brb with the correct values

SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED, thanks Jim!
Hi

While working on my Uno game, I discovered something very strange.
I wanted to make an animation in which a card moves from one place to another, and therefore I need to determine the angle between the position is is now, and the position it has to travel to. To do this, I use math.atan2( xdifference, ydifference), which return an angle in radians.

When I let the computer software (runs OS 3.2) calculate everything works fine, and the card moves from the position it is to where it has to go, like it should.
Buut when I run exactly the same code, just transfered via usb, on my calc (nspire cx cas, os 3.1.0.392), it doesn't work. The angle it returns is about half the size of the one from the student software, while using exact the same calculations.

Am I not seeing something? Or is there some mess up with radians vs. degrees on software and calc?

Here's the code:
function TheGame:timer()
    local xDif = math.abs(self.movingCardPos[1]-self.defPos[1])
    local yDif = math.abs(self.movingCardPos[2]-self.defPos[2])
    local dirX = xDif/(self.movingCardPos[1]-self.defPos[1])
    
    if xDif<5 and yDif<5 then
        timer.stop()
        table.insert(self.pack, self.movingCard)
        self.movingCard = nil
        self.movingCardPos = nil
    else
        local tan = math.atan2( yDif, xDif )
        if dirX>0 then
            self.movingCardPos[1] = self.movingCardPos[1]-4*math.cos(tan)
        else
            self.movingCardPos[1] = self.movingCardPos[1]+4*math.cos(tan)
        end
        self.movingCardPos[2] = self.movingCardPos[2]-4*math.sin(tan)
        platform.window:invalidate()
    end
end

screenie pc:


screenie calc:


The number in the corner is the value returned by math.atan2(), of which you can see it differs

Solved: I had to update the screenSize after init, because that seems to return 0 at the beginning. Thanks Jim!!