Navigator significantly broken in 1.7 (Major Bug)

I created a bug report (CIDER-90), but thought I’d post it here in case anyone else has seen it:

If you have a global function, the parser in 1.7 is unable to reference it.

To recreate, simply add a new Lua file, add the sample code below, and save it. Open Navigator. There, you will see _G.myGlobalFunction(sText).
Double click on it, which would normally take you to the function, and instead it opens a new file called globals.lua
This is not the correct behavior.

If I remove _G. from it, it works properly.

[code]

function _G.myGlobalFunction(sText )

print (“sText”)

end

[/code] [import]uid: 13784 topic_id: 30975 reply_id: 330975[/import]

Hello Marble,

Thanks for the report. Working on a fix.
[import]uid: 55057 topic_id: 30975 reply_id: 123930[/import]

Latest version is ?

@Marbles @ M.Y.developers
“If you have a global function, the parser in 1.7 is unable to reference it.”

Where/how did you get v1.7? The latest I have is v1.6.98beta.

Also, since the last update it keeps asking for a license when opened. The only one I have is from the non beta I purchased, but that doesn’t appear to work as I still keep getting the same message on every Glider start up now. [import]uid: 37683 topic_id: 30975 reply_id: 123940[/import]

1.7

Check your email, you should have gotten a link. [import]uid: 13784 topic_id: 30975 reply_id: 123959[/import]

FYI @M.Y.developers -

I found a pretty significant usability bug.

I still haven’t found the exact steps to recreate it but it keeps locking the file I am editing and not allowing me to save changes.

It has something to do with the Dubugger and the a sequence of debugging, editing, running, editing, debugging.

When it manifests, you can’t save any of your code changes and you have to restart Glider. If you don’t copy your work, you lose it!! [import]uid: 13784 topic_id: 30975 reply_id: 123960[/import]

I filed a bug report, as usual. [import]uid: 13784 topic_id: 30975 reply_id: 123961[/import]

Hmm… I didn’t get an email.
Is 1.7 officially out? [import]uid: 114363 topic_id: 30975 reply_id: 123971[/import]

No email received here either… [import]uid: 37683 topic_id: 30975 reply_id: 123987[/import]

@All,
1.7 is not officially out yet. The version Marble is referring to is 1.6.98. Its close to release, but not quite yet. Hopefully we can fix the major issues (ie the file locking issue) and release it soon.

@Marble,
Does the lock only occur with your main.lua? Does it give you any sort of display message informing you the file is locked? If you have Corona running it might take ownership of your files while it is compiling, we find that if it is stuck at a breakpoint during the main chunk it will have file locks on. Any hints on replicating this bug will be very helpful!

Regards,
M.Y. Developers [import]uid: 55057 topic_id: 30975 reply_id: 123994[/import]

Beta v1.6.98 won’t let me use Corona but only the basic Lua option can be selected in options.

Makes it useless at present and the ‘official’ release I have is at v1.5.3 which is to broken to use long term. Hopefully v1.7 will be along soon as things certainly are getting better with each little update :slight_smile:

Not a complaint, just observations. Thanks for all the hard work guys. [import]uid: 37683 topic_id: 30975 reply_id: 124000[/import]

No. I have a modules called functions. Yes, it says it can’t open the file for exclusive access: functions.lua@a82haf89wh9fa839h:234982 (or something).

Maybe it is in the version or change tracking?

Yes - It occurs while I am debugging. Last night, was doing lots of jumping around with breakpoints, etc. It almost always occurred when I was at a breakpoint or an error, and I edited the file. Sometimes it would close and restart Corona (as expected).

Other times, it would just pause, then alert it couldn’t save when I did a CTRL+S (habit, I do it a lot)

And yes - sorry - this 1698 build I’m running I call 1.7… I will stop doing that. [import]uid: 13784 topic_id: 30975 reply_id: 124001[/import]

@Whiteball
Sorry it seems the IDE is using an older license. Could you send us an email? We will email you the license key.

@Marble,
No problem. We pushed an autoupdate for the Navigator bug. After updating you will see an new menu item help->upload logs. This will zip up the IDE logs (ie crashes/exceptions/errors) and upload it to our server. If you could do that it would help us a lot. As for the file access issue, we will probably have to talk to the Corona team as it seems to be related to the double print bug. As you probably know the simulator will run through the main chunk twice; the first time it locks the files but subsequent times it will not. Strange issue but we will try to get it fixed.

Regards,
M.Y. Developers
[import]uid: 55057 topic_id: 30975 reply_id: 124005[/import]

I am having the same issue as Whiteball but I’m on version 1.6.99 [import]uid: 58885 topic_id: 30975 reply_id: 124064[/import]

@All,

You should have gotten an email from us with your free upgrade license. This should address all licensing issues. Please let us know if you did not receive it and also make sure to check your spam box.

Regards,
M.Y. Developers [import]uid: 55057 topic_id: 30975 reply_id: 124151[/import]

I got the 1.7 and have updated. If it does the locking, I will do the upload logs before closing it. [import]uid: 13784 topic_id: 30975 reply_id: 124182[/import]

Hello Marble,

Thanks for the report. Working on a fix.
[import]uid: 55057 topic_id: 30975 reply_id: 123930[/import]

Latest version is ?

@Marbles @ M.Y.developers
“If you have a global function, the parser in 1.7 is unable to reference it.”

Where/how did you get v1.7? The latest I have is v1.6.98beta.

Also, since the last update it keeps asking for a license when opened. The only one I have is from the non beta I purchased, but that doesn’t appear to work as I still keep getting the same message on every Glider start up now. [import]uid: 37683 topic_id: 30975 reply_id: 123940[/import]

1.7

Check your email, you should have gotten a link. [import]uid: 13784 topic_id: 30975 reply_id: 123959[/import]

FYI @M.Y.developers -

I found a pretty significant usability bug.

I still haven’t found the exact steps to recreate it but it keeps locking the file I am editing and not allowing me to save changes.

It has something to do with the Dubugger and the a sequence of debugging, editing, running, editing, debugging.

When it manifests, you can’t save any of your code changes and you have to restart Glider. If you don’t copy your work, you lose it!! [import]uid: 13784 topic_id: 30975 reply_id: 123960[/import]

I filed a bug report, as usual. [import]uid: 13784 topic_id: 30975 reply_id: 123961[/import]