Thank you!

Suspiciously I do have other objects that change text size but I'd expect this to be thread isolated?

At the time of a win I should not be changing the text size for anything.

Win = class()

function Win:init()
    -- you can accept and set parameters here
    self.colorR = math.random(1,255)
    self.colorB = math.random(1,255)
    self.colorG = math.random(1,255)

end

function Win:draw()
    -- Codea does not automatically call this method
   -- textSize(90)
    self.colorR = math.random(1,255)
    self.colorB = math.random(1,255)
    self.colorG = math.random(1,255)
    fill(self.colorR,self.colorB,self.colorG)
    textSize(90)
    text("YOU WIN",WIDTH/2,HEIGHT/2)

end

function Win:touched(touch)
    -- Codea does not automatically call this method
end

If this is intended, can we put a warning in the documentation somewhere?

function setup()
    physics.gravity(0,0)
    parameter.boolean("Crash",false)

    circle1= physics.body(CIRCLE, 50)
    circle1.x,circle1.y=100,400
    circle1.type=DYNAMIC
    circle1.linearVelocity=vec2(80,0)

    circle2=physics.body(CIRCLE,50)
    circle2.x,circle2.y=600,400
    circle2.linearVelocity=vec2(-50,0)
    circle2.type=DYNAMIC
    print("I want to delete the left hand circle when they collide")
    print("With Crash turned OFF, circle is destroyed in draw function")
    print("With Crash turned ON, circle is destroyed in collide function")
end

function draw()
    background(200)
    fill(0,0,255,100)
    ellipseMode(CENTER)
    if destroy then
        circle1:destroy()
        circle1=nil
        destroy=nil
    end
    if circle1 then ellipse(circle1.x,circle1.y,100) end
    ellipse(circle2.x,circle2.y,100)
end

function collide(contact)
   if Crash then --destroy circle here
        circle1:destroy()
        circle1=nil
   else
       destroy=true --tell draw to destroy circle
   end
end

First time I just assumed some memory glitch, second time it must be a bug... V 1.5.2 (18)

If I can figure out what started ill post it. This time I was inputting a "line". After I ran my code the line wasn't there and I noticed it said

Something like

Line(30.50,10,20) Instead of

Line(30,50,10,20)

But not sure i can reproduce it on demand.

Closing the code and reopening corrects it.

Every time you reset the program you'll get different values for the various bits of currentTouch, and it'll eventually crash.

Running the latest version of codea (1.5.1)

local defPoints = {vec2(0,5), vec2(3,0), vec2(-3,0), vec2(0,5)}
self.body = physics.body(POLYGON, unpack(defPoints))
self.body.mass = 1

It seems that the last line causes the crash as soon as I try to run the project (I disabled everything in my draw() to make sure it wasn't something else causing the crash - commenting out the last line does in fact fix the crash). I get the following on my device's console output:

Mar 18 10:52:53 MA-iPad-mini Codea[13454] <Error>: libMobileGestalt copySystemVersionDictionaryValue: Could not lookup ReleaseType from system version dictionary
��Mar 18 10:52:53 MA-iPad-mini Codea[13454] <Warning>: (
        0
    )
��Mar 18 10:52:53 MA-iPad-mini Codea[13454] <Warning>: (
        0,
        "0.5"
    )

function setup()
    rectMode(CENTER)
    parameter.text("input")
end

function draw()
    background(40, 40, 50)
    
    if isKeyboardShowing() then
        kb="true"
    else
        kb="false"
    end
    
    fill(255)
    text("isKeyboardShowing       "..kb,200,500)
    rect(200,800,200,50)
    rect(200,700,200,50)
    
    fill(255,0,0)
    text("show keyboard",200,800)
    text("hide keyboard",200,700)
end

function touched(t)
    if t.x>100 and t.x<300 and t.y>775 and t.y<825 then
        showKeyboard()
    end
    if t.x>100 and t.x<300 and t.y>675 and t.y<725 then
        hideKeyboard()
    end
end

So not rotated 180 degrees, left right is ok but up down is switched. This is the case for both front and back camera.

Can you guys at the controls please fix this ?

Thanks for your great work.

Erik

So say for instance I make a function which has this in it : box.linearVelocity = vec2(bl.x+steer.xspeedDeltaTime*3-bl.x/25,box.linearVelocity.y), because this line wraps itself to the next, if I try to place my caret just after vec2, it ends being somewhere near box.linearVelocity.y and editing text around there, i hope someone knows what I mean!

I have a program with two meshes. One has a shader attached to it, the other doesn't. The second (without the shader) has a texture. When I draw them then only the mesh with a shader appears.

Experimenting leads to the following. Let's call the meshes a and b.

1. a has shader, b has texture => a drawn, b not.
2. a has shader, b does not have texture (but has colour) => a drawn, b drawn.
3. a does not have shader, b has texture => a drawn, b drawn
4. a has shader, b has default shader and texture => a drawn, b drawn
5. a has shader but is not drawn, b has texture => a not drawn, b drawn

It also appears that the order of drawing of a and b is immaterial. I think I see a "flash" whereby b is drawn initially and then disappears on subsequent draws.

So my guess is that when a is drawn then a shader is actually installed for b as well and this shader does not render the texture.

I've gotten round it by explicitly giving b a shader (case 4). I'll try to pare down my program to a MWE that shows the bug.

I call function EngineCalcs() from inside function (draw) to perform all of my calculations. The program is fairly simple and uses the input values to calculate the ideal thermodynamic values for a gasoline engine based on changes in the parameters.

--# Main
-- ScrollCrash

a = 0
b = 1
c = 2
d = 3
e = 4
f = 5
g = 6
h = 7

-- Use this function to perform your initial setup
function setup()
    parameter.watch("a")
    parameter.watch("b")
    parameter.watch("c")
    parameter.watch("d")
    parameter.watch("e")
    parameter.watch("f")
    parameter.watch("g")
    parameter.watch("h")
end

-- This function gets called once every frame
function draw()
a = a + 1
b = b + 1
c = c + 1
d = d + 1
e = e + 1
f = f + 1
g = g + 1
h = h + 1

end

I have now had a few times issues with the shader lab.

Specifically, If I have a particularly large involve shader, I can go in there, make a change, exit the lab and run my program. Everything is fine and the changes are visible in game.

But then, I end the game click the shader and edit to get back into the lab and my shader has reverted to it's previous state losing my change. This is without exiting codea or anything.

Very odd.

Sorry, I have no idea how to check what version I am running.

P.S. Amazing app!!!

First part

function setup()
    print( vec2() )
    print( vec3() )
    print( vec4() )
end

This results in:

(0.000000, 0.000000)

(0.000000, 0.000000, 0.000000)

(0.000000, 0.000000, 0.000000, 1.000000)

I even had this problem when filling the membership form... I had to hide the keyboard to get to the last couple of options, then type blind because the keyboard was covering the input box.

(I'm working on an iPad Mini. I've got the same problem in both portrait and landscape view. )

-- spazzing ball

function setup()
    displayMode(FULLSCREEN)
    ball = {x = WIDTH/2, y = HEIGHT/2, size = 20, color = color(255, 255, 255, 255), tweens = {}}
end

function draw()
    if #ball.tweens == 0 then
        setupTweens()
    end
    background(40, 40, 50)
    strokeWidth(2)
    fill(ball.color)
    ellipse(ball.x, ball.y, ball.size)
end

function setupTweens()
    for i=1, 10 do
        --table.insert(ball.tweens, {x = makeTween(WIDTH), y = makeTween(HEIGHT)})
        table.insert(ball.tweens, {x = 0, y = 0})
    end
    tween.path(ball, 2 * #ball.tweens, ball.tweens, tween.easing.linear)
end

function makeTween(max)
     return math.random(ball.size/2, max - ball.size/2)
    --newY = math.random(ball.size/2, HEIGHT - ball.size/2)
    --return {x = newX, y = newY}
end

When I run the program, however, I get this error message from the string base class:

error: [string "-------------------------------------------..."]:474: bad argument #2 to 'min' (number expected, got table)

Any ideas?

function setup()
    et=0
end

function draw()
    background(40, 40, 50)
    
    fill(255)
    text(math.floor(ElapsedTime),300,800)
    
    if ElapsedTime-et > 3 then    -- draw lines and print text every 3 seconds
        stroke(255)
        strokeWidth(2)
        
        for z=1,15 do                        -- change value to 10,15,or 20
            line(200+z*5,200,200+z*5,600)    --draws 10, 15, 20 lines
        end
        
        print("drawing lines")
        et=ElapsedTime
    end
    
end

I'm out of options on it, and I would like it since I had to restore my iPad and lost it.

Edit: changed the code to trigger the issue sooner. Within a few secs it will print false

function setup()
    nextT = 0
    bodies = {}
    physics.gravity(vec2(0,-10000))
end

function draw()
    if ElapsedTime > nextT then
        for _,body in ipairs(bodies) do body:destroy() end
        bodies = nil
        bodies = makeBodies()
        nextT = ElapsedTime + .1
    end
end

function makeBodies()
    local bodies = {}
    local box = physics.body(POLYGON,vec2(0,0),vec2(10,0),vec2(10,10),vec2(0,10))
    box.x = 20
    box.y = 361
    box.info = {mytype="box"}
    table.insert(bodies,box)
    
    local ground = physics.body(POLYGON,vec2(0,0),vec2(WIDTH,0),vec2(WIDTH,20),vec2(0,20))
    ground.x = 0
    ground.y = 360
    ground.type = STATIC
    ground.info = {mytype="ground"}
    table.insert(bodies,ground)
    return bodies
end

function collide(contact)
    if contact.bodyA.info==contact.bodyB.info then 
        print(contact.bodyA==contact.bodyB,ElapsedTime)
    end
end

function setup()
end

function draw()
    background(40, 40, 50)
end

function touched(t)
    if t.state==BEGAN then
        print("began")
    end
    if t.state==MOVING then
        print("moving")
    end
    if t.state==ENDED then
        print("ended")
    end
end

math.random(0,10) --Generates no. between 0-10. 
variable_one = math.random(0,10) --Tells PC that variable is a random no


local input = nil --The input currently is nothing.

print("Enter a number between 0-10 that you think the computer is thinking of.") 

Io.write("Enter number (0/1/2/3/4/5/6/7/8/9/10)")
Answer=io.read()
If answer = "variable_one" then
   (print("Correct."))
else
    print("You were wrong!")
end

I get the following error message: '=' expected near 'answer.' This program is meant to ask the user what number it is thinking of. If the user enters the correct value, then the program prints "Correct" and the program ends. This is my first attempt at my own program based on looking at YouTube tutorials.

Is this a known issue or limitation when rendering to an image?

function draw() screenCap = image(WIDTH, HEIGHT) setContext(screenCap) sceneDraw() setContext() sprite(screenCap,WIDTH/2,HEIGHT/2) end

function setup()
    displayMode(FULLSCREEN)
    
    v=300    -- change to 400, 500, 600
    
    c=color(255,255,255)
    img = image(v,v)
    img:set(v,v,c)    -- draw white dot at v,v
       
    setContext(img)    
    fill(175, 179, 75, 255)
    rect(1,1,v,v)    -- draw rect at 1,1 width v, height v
    
    stroke(251, 0, 0, 255)
    strokeWidth(3)
    line(1,1,v,v)    -- draw diagonal line from 1,1 to v,v
end

function draw()
    background(0,0,0)
    sprite(img,WIDTH/2,HEIGHT/2)    -- draw image centered on screen
end

But I can't believe how often I have to leave the app to avoid bugs.

I have a project that works great, but only the first time it's run. Usually the second or third time will throw errors. The reset button doesn't help.

Sometimes leaving the project and starting it again from within Codea is enough, but sometimes I have to leave the app completely before it will run properly again. Sometimes I even have to terminate Codea from the app switcher.

Needless to say, this makes coding somewhat laborious, since I have to exit all the time. Is this SOP around here?

I'm drawing a bunch of rotating "stars", and they cover each other up. Screenshot: http://i.imgur.com/SKZE8l.jpg

Is this a bug, a quirk, or a feature I'm just unaware of?

Source, if it helps:

-- 3D Test

-- Use this function to perform your initial setup
local starcount = 1000
local starrange = 1000
function setup()
    -- generate star locations
    stars = {}
    for i = 1, starcount do
        stars[#stars + 1] = {
            x = math.random(starrange);
            y = math.random(starrange);
            z = math.random(starrange);
            rotation = 0; -- initial rotation, changes every frame
            drotation = math.random(-180, 180); -- rotation speed in degs/scnd
        }
    end
    camx = starrange / 2
    camy = starrange / 2
    camz = starrange / 2
    angle = 0
    parameter("camx", -starrange / 2, starrange * 1.5)
    parameter("camy", -starrange / 2, starrange * 1.5)
    parameter("camz", -starrange / 2, starrange * 1.5)
    parameter("angle", 0, 360)
end

-- This function gets called once every frame
function draw()
    ellipseMode(CORNER)
    fill(255, 255, 255)
    stroke(255, 248, 0, 255)
    -- This sets a dark background color 
    background(0, 0, 0, 255)

    -- This sets the line thickness
    strokeWidth(5)

    -- Do your drawing here
    -- setup 3D matrix
    pushMatrix()
        -- setup perspective
        perspective()
            camera(
                -- eye location
                camx, camy, camz,
                -- look vector
                camx + math.sin(math.rad(angle)),
                camy,
                camz + math.cos(math.rad(angle))
            )
            -- draw stars
            for i, v in ipairs(stars) do
                -- rotate star
                v.rotation = v.rotation + v.drotation * DeltaTime
                -- transform to star-local coordinate system
                pushMatrix()
                    translate(v.x, v.y, v.z)
                    rotate(v.rotation, 0, 1, 0)
                    -- draw primitive to represent star
                    ellipse(-20, -20, 40, 40)
                popMatrix()
            end
        -- undo perspective
        ortho()
    popMatrix()
end

this is the report error in the organizer window of Xcode:

Incident Identifier: F174F0E7-7193-493F-A937-74D93B75315C
CrashReporter Key:   10651cd8b5e6d476651ce356a380205e09c93f93
Hardware Model:      iPad2,2
Process:         Codea [2681]
Path:            /var/mobile/Applications/5F1F08C1-D515-42B6-B3A6-4656E68781D5/Codea.app/Codea
Identifier:      Codea
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process:  launchd [1]

Date/Time:       2012-08-13 14:21:25.977 +0200
OS Version:      iPhone OS 5.0.1 (9A405)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000020
Crashed Thread:  0

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_c.dylib               0x32f15c74 memcpy$VARIANT$CortexA9 + 244
1   Codea                           0x00137b08 0x95000 + 666376
2   Codea                           0x0019d58a 0x95000 + 1082762
3   Codea                           0x0019d6de 0x95000 + 1083102
4   Codea                           0x001a6eb4 0x95000 + 1121972
5   Codea                           0x001a7a5e 0x95000 + 1124958
6   Codea                           0x0019d6e8 0x95000 + 1083112
7   Codea                           0x00198882 0x95000 + 1063042
8   Codea                           0x0019d0d4 0x95000 + 1081556
9   Codea                           0x0019d888 0x95000 + 1083528
10  Codea                           0x0019885a 0x95000 + 1063002
11  Codea                           0x000a5304 0x95000 + 66308
12  Codea                           0x000ac446 0x95000 + 95302
13  UIKit                           0x32817508 -[UIWindow _sendTouchesForEvent:] + 312
14  UIKit                           0x32816efa -[UIWindow sendEvent:] + 374
15  UIKit                           0x327fd4e6 -[UIApplication sendEvent:] + 350
16  UIKit                           0x327fcd26 _UIApplicationHandleEvent + 5802
17  GraphicsServices                0x30b4fdec PurpleEventCallback + 876
18  CoreFoundation                  0x342e1afc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 8
19  CoreFoundation                  0x342e12c8 __CFRunLoopDoSources0 + 208
20  CoreFoundation                  0x342e006e __CFRunLoopRun + 646
21  CoreFoundation                  0x342634d6 CFRunLoopRunSpecific + 294
22  CoreFoundation                  0x3426339e CFRunLoopRunInMode + 98
23  GraphicsServices                0x30b4efc6 GSEventRunModal + 150
24  UIKit                           0x3282b73c UIApplicationMain + 1084
25  Codea                           0x00097e18 0x95000 + 11800
26  Codea                           0x00097dd8 0x95000 + 11736

Thread 1 name:  Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0   libsystem_kernel.dylib          0x36d743b4 kevent + 24
1   libdispatch.dylib               0x3330af74 _dispatch_mgr_invoke + 708
2   libdispatch.dylib               0x3330ac92 _dispatch_mgr_thread + 30

Thread 2:
0   libsystem_kernel.dylib          0x36d84cd4 __workq_kernreturn + 8
1   libsystem_c.dylib               0x32eaa30a _pthread_wqthread + 610
2   libsystem_c.dylib               0x32eaa09c start_wqthread + 0

Thread 3:
0   libsystem_kernel.dylib          0x36d84cd4 __workq_kernreturn + 8
1   libsystem_c.dylib               0x32eaa30a _pthread_wqthread + 610
2   libsystem_c.dylib               0x32eaa09c start_wqthread + 0

Thread 4 name:  WebThread
Thread 4:
0   libsystem_kernel.dylib          0x36d74010 mach_msg_trap + 20
1   libsystem_kernel.dylib          0x36d74206 mach_msg + 50
2   CoreFoundation                  0x342e141c __CFRunLoopServiceMachPort + 120
3   CoreFoundation                  0x342e0154 __CFRunLoopRun + 876
4   CoreFoundation                  0x342634d6 CFRunLoopRunSpecific + 294
5   CoreFoundation                  0x3426339e CFRunLoopRunInMode + 98
6   WebCore                         0x33794128 _ZL12RunWebThreadPv + 396
7   libsystem_c.dylib               0x32eafc16 _pthread_start + 314
8   libsystem_c.dylib               0x32eafad0 thread_start + 0
.... 

Thread 0 crashed with ARM Thread State:
    r0: 0x2fe923d8    r1: 0x00000020      r2: 0xffffffc6      r3: 0x2fe923b8
    r4: 0x00000001    r5: 0x0d1386f0      r6: 0x00000001      r7: 0x2fe923c8
    r8: 0x0d5adf34    r9: 0x001fbcec     r10: 0x029aa280     r11: 0x00000000
    ip: 0xc0000000    sp: 0x2fe923c0      lr: 0x00137b0f      pc: 0x32f15c74
  cpsr: 0x80080010

Binary Images:
   0x95000 -   0x1fafff +Codea armv7  <11b8b7d0f6f630bca18961b8abaccf19> /var/mobile/Applications/5F1F08C1-D515-42B6-B3A6-4656E68781D5/Codea.app/Codea
  ...etc.

I dont know how to solve this problem, so here i am asking you for some help :] Filled an issue here: https://bitbucket.org/TwoLivesLeft/codea/issue/181/multiple-touch-crash

I don't remember this being mentioned, but I ran into this problem with the editor whenever I do a multi line indent. I set up this small function as a simple example. I you select the 3 print statements in the 1st example and do a mullti line indent using the indent key on the upper left of the keyboard, you'll end up with the 2nd example. The 1st end statement has an extra e (eend) at the beginning. The cursor can't be placed after the eend, but it goes between the n and the d. The color is also different for the first e. Also, if you start trying to delete and add lines where the end statements are, you end up with other weird things. I can't give a specific example for that.

CODE BEFORE MULTI LINE INDENT

function xx()
    for x=1,5 do
    for y=1,5 do
    for z=1,5 do
    print(x)
    print(y)
    print(z)
    end
    end
    end
end


CODE AFTER MULTI LINE INDENT

function xx()
    for x=1,5 do
    for y=1,5 do
    for z=1,5 do 
         print(x)
         print(y)
         print(z)
   eend
    end
    end
end

I have purchased the Dark Theme for Codea but trying to activate it causes the app to constantly crash. I then have to delete the app and download again from the app store. It will then ask for my app store password every time I open Codea, if I put the password in the app will then continue to keep crashing until it is removed again. Has anyone else experience this, and is there a work around for it?

Many Thanks Gavin

    text("Hello there, this is Simon's first program written on the ipad",CurrentTouch.x,CurrentTouch.y)

You can see that Codea duplicates some of the text and spits an error. I only tested with this particular line of code so can't confirm for others. Cheers Simon