Lua Glider IDE breakpoint error

Glider (IDE)
#1

Hello,

I am getting an error when using the Lua Glider IDE to try and set a breakpoint in a function in my project. When I run my project it successfully hits the breakpoint; however, it also throws an error that is displayed on the console. I have attached a screen capture of the exact error. The end result of the error is that none of the debug capabilies (e.g. step over, step into, continue, etc…) work after the error is thrown and I end up have to restart the project.

This is the version of LuaGlider IDE that I am using:
Product Version: LuaGliderv19 201302132200

I’m using: Corona SDK on Windows
Corona build number: 2012.971

Has anyone else run into this issue?

Thanks,

#2

Hello Avazquez,

Sorry about this problem it is due to a feature to extract keys from display objects and other lua tables when they contain keys that do not show up with “pairs.” Take the following code snippet for instance

local circle = display.newCircle(0, 0, 20) for i,v in pairs(circle) do print(i,v) end --OUTPUT: --\_class table: 026A2978 --\_proxy userdata: 026BB690

The reason the keys such as x,y,rotation, alpha, etc do not show up is that these are not stored in the lua table itself but rather in some other model (the proxy.) Since we know ahead of time to ask for the keys we are able to show you their values in the variables tab. Unfortunately the network table does not just return nil when given an invalid key but rather errors out.

We will look into better ways to solve this problem. You can temporarily fix this problem by disabling this feature for now. Here is how:

  1. Help->User Directory

  2. Open up System plugins->corona->plugin.lua

  3. Please delete the lines that read like this:

    extraSymbols = { “x”,“y”,“rotation”,“alpha”,“width”,“height”,“isVisible”,“xReference”,“yReference”,“xScale”,“yScale”}

After saving the file you should not have the problem anymore.

Regards,
M.Y. Developers

#3

Cool Thanks. The issue I was having of breakpoints not working at all seems to have been fixed by updating my corona sdk to the latest build

2013.1137

#4

Hello Avazquez,

Sorry about this problem it is due to a feature to extract keys from display objects and other lua tables when they contain keys that do not show up with “pairs.” Take the following code snippet for instance

local circle = display.newCircle(0, 0, 20) for i,v in pairs(circle) do print(i,v) end --OUTPUT: --\_class table: 026A2978 --\_proxy userdata: 026BB690

The reason the keys such as x,y,rotation, alpha, etc do not show up is that these are not stored in the lua table itself but rather in some other model (the proxy.) Since we know ahead of time to ask for the keys we are able to show you their values in the variables tab. Unfortunately the network table does not just return nil when given an invalid key but rather errors out.

We will look into better ways to solve this problem. You can temporarily fix this problem by disabling this feature for now. Here is how:

  1. Help->User Directory

  2. Open up System plugins->corona->plugin.lua

  3. Please delete the lines that read like this:

    extraSymbols = { “x”,“y”,“rotation”,“alpha”,“width”,“height”,“isVisible”,“xReference”,“yReference”,“xScale”,“yScale”}

After saving the file you should not have the problem anymore.

Regards,
M.Y. Developers

#5

Cool Thanks. The issue I was having of breakpoints not working at all seems to have been fixed by updating my corona sdk to the latest build

2013.1137