Lua Glider issues on Mac

@ M.Y.developers

Thanks. I had the version downloaded from your website a few days ago which didn’t have that pref option. I updated and now it has it and I have set it to “scan only stubs”. So far half a day without any issues, so that may have solved it. Thanks for all your help!

BTW, what feature am I losing by turning off scanning. Was that indexing for faster searches or something else?

@zrm310,

Glad that is working for you.

BTW, what feature am I losing by turning off scanning. Was that indexing for faster searches or something else?

In order to have some advanced features such as:

  • Code navigation (ie go to declaration/implementation)
  • Usage search
  • Globals highlighting
  • Class aware/parameterized code completion
  • Unused variable detection

Glider needs to scan and analyze your lua code. Since lua is a dynamic language the only way to figure out the input/outputs of a function are is to scan through it and “execute” it. In the end this allows us to infer stuff about your code to give you the features listed above.

If you do not use these features then you will probably be happier just turning off the scanning. You will still get Corona autocomplete and a plain text index based autocomplete of the current file. You should turn on scanning when you wish to experiment with the above features. 

Regards,

M.Y. Developers

@zrm310,

Just making sure it is working better for you. Have you encountered any issues since then?

Regards,

M.Y. Developers

@ M.Y.developers,

Thanks for checking. It’s a lot better and usable for hours every day. It’s a great tool and become my IDE of choice. 

I only regret not be able to use the advanced features you mention as my project grows larger, since whenever I turn on scanning it grinds the program to a halt and makes it unusable within 20 minutes.

Any idea why the scanning is so slow for even a small project? Is it possibly incorrectly also scanning non lua files in the project directory?

Hello Zrm310,

We are constantly improving the storage engine so you may want to try this:

http://view.xscreenshot.com/c5891817cb86392a0bf2164ecb0f864b

This should fix the slowness problem if it stems from memory usage. 

Regards,

M.Y. Developers

Hi M.Y.developers,

Thanks for the suggestion; I’ll give it a try. Not sure if that’s a new option, as “Use RAM storage” was already checked on mine. But I’ll switch the scanner detail back to “Scan main.lua…” and see if the same slowdown happens or not.

When everything works, I love your program. I’m new to Lua and Corona so I’m still amassing tools, but this is the only IDE I’ve found that approaches other environments I’m used to.

Hello Zrm310,

Sorry about the ambiguity, we meant to uncheck the RAM storage option so that it can swap stuff to the disk when needed. However if you have it checked and it is working for you that is an even better sign. We have got quite a few more features planned so if you miss something from your other environments then let us know.

Regards,

M.Y. Developers

My Version of Lua Glider has stopped working and is now hogging 100% of the CPU upon start up. Tried uninstalling it and then re-installing it and no prevail. Everytime it starts it just freezes? I have the latest OS on my mac and Lua Glider, please help?

Hello Evanbanana,

Please go to this folder:

http://view.xscreenshot.com/e21a086926e8bca538b7a40583a9e891

and delete the config->Preferences folder.

This should start up Glider. Please send the logs via help->upload logs when it starts up. Did this problem occur just randomly or after some event?

Regards,

M.Y. Developers

@M.Y.developers

I have a thinking of the slow scanning. It happens whenever I requires some bulky third party library files such as MTE, lime, particle candy etc. I suggest another option for the user as “Scan Only Current File” without “+ requires”. I guess it may help. You know library such as MTE consists 12,177 lines of code.

Hello Wilsonwansun,

Thanks for letting us know about this. We regularly test with Particle/text candy, Lime, and as many other lua libs we can find on github and other sources. Never heard about the MTE library however, can you point us to the source? The Scanner will only scan files up to around 10k lines of code for performance reasons.

Regards,

M.Y. Developers

Cheers managed to find the folder and remove preferences which has done the trick. Uploading logs as we speak!

Hello Evan,

Thanks for the logs. Seems like a strange issue in the Java rendering pipeline for Mac. The source is coming from the image preview panel. Did the crash occur after previewing an image (perhaps a very large one)?

Regards,

M.Y. Developers

My Version of Lua Glider has stopped working and is now hogging 100% of the CPU upon start up. Tried uninstalling it and then re-installing it and no prevail. Everytime it starts it just freezes? I have the latest OS on my mac and Lua Glider, please help?

Hello Evanbanana,

Please go to this folder:

http://view.xscreenshot.com/e21a086926e8bca538b7a40583a9e891

and delete the config->Preferences folder.

This should start up Glider. Please send the logs via help->upload logs when it starts up. Did this problem occur just randomly or after some event?

Regards,

M.Y. Developers

@M.Y.developers

I have a thinking of the slow scanning. It happens whenever I requires some bulky third party library files such as MTE, lime, particle candy etc. I suggest another option for the user as “Scan Only Current File” without “+ requires”. I guess it may help. You know library such as MTE consists 12,177 lines of code.

Hello Wilsonwansun,

Thanks for letting us know about this. We regularly test with Particle/text candy, Lime, and as many other lua libs we can find on github and other sources. Never heard about the MTE library however, can you point us to the source? The Scanner will only scan files up to around 10k lines of code for performance reasons.

Regards,

M.Y. Developers

Cheers managed to find the folder and remove preferences which has done the trick. Uploading logs as we speak!

Hello Evan,

Thanks for the logs. Seems like a strange issue in the Java rendering pipeline for Mac. The source is coming from the image preview panel. Did the crash occur after previewing an image (perhaps a very large one)?

Regards,

M.Y. Developers