@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