Auto Complete Not Working For .lua Files In Subdirectory

Glider (IDE)
#1

Hi,

I am having an issue with the auto complete not working for any .lua files in subdirectories.

 

For example:

[lua]

 

local GameEngineConstants = require “scripts.game_engine_constants”

local Blocks = require"scripts.Blocks"

local WordList = require"scripts.WordList"

local WordDictionary = require"scripts.WordDictionary"

[/lua]

 

If I attempt to access any of these tables, the auto complete does not work. If I change it to 

[lua]

local GameEngineConstants = require “game_engine_constants”

local Blocks = require"Blocks"

local WordList = require"WordList"

local WordDictionary = require"WordDictionary"

[/lua]

the autocomplete works but then the build fails. 

#2

I’ve created a bug regarding this issue in the issue tracker for Glider. You can find it here:

https://mydevelopers.atlassian.net/browse/CIDER-149

#3

Grmbl… after buying the product I could now update it, version 1.7.2 fixes the issue :) . Will close the jira issue as well.

update: OK could not close the jira issue, but added a comment in stead.

#4

Hello Everyone,

One of the reasons it is taking us a while to release the next version is because we are working on better analysis of multi-file and multi-library projects. Static analysis of a dynamic language like lua requires “running” the code to figure out what it does. This is in contrast to a statically typed language (ie Java) where most the important information (ie return values, parameter types, etc) comes from just looking at the function signature. Version 1.7.x of Glider analyzes the current file well but only weakly analyzes its dependencies. We are working on much more sophisticated project wide indexing in Glider 1.9. Many things needed to be changed for this, including putting everything in a database to prevent out of memory errors, and subsequent low level optimizations to get acceptable speeds. These problems turned out to be non-trivial. Thanks for your patience on this matter.

Regards,

M.Y. Developers

#5

I’ve created a bug regarding this issue in the issue tracker for Glider. You can find it here:

https://mydevelopers.atlassian.net/browse/CIDER-149

#6

Grmbl… after buying the product I could now update it, version 1.7.2 fixes the issue :) . Will close the jira issue as well.

update: OK could not close the jira issue, but added a comment in stead.

#7

Hello Everyone,

One of the reasons it is taking us a while to release the next version is because we are working on better analysis of multi-file and multi-library projects. Static analysis of a dynamic language like lua requires “running” the code to figure out what it does. This is in contrast to a statically typed language (ie Java) where most the important information (ie return values, parameter types, etc) comes from just looking at the function signature. Version 1.7.x of Glider analyzes the current file well but only weakly analyzes its dependencies. We are working on much more sophisticated project wide indexing in Glider 1.9. Many things needed to be changed for this, including putting everything in a database to prevent out of memory errors, and subsequent low level optimizations to get acceptable speeds. These problems turned out to be non-trivial. Thanks for your patience on this matter.

Regards,

M.Y. Developers

#8

Hello Everyone,

Please try the new Glider 1.9.08. There is be much better multi-file integration in this version. Please let us know how it works out for you. The upgrade is free and the trial keys are reset so you can try it out again if you wish.

Regards,

M.Y. Developers

#9

Version 1.9 fixes the issue. Thanks. On a side note is there a way to activate autocomplete without having to hit control + space?  

#10

Hello Quantum,

Here you go:

http://forums.coronalabs.com/topic/34907-19-auto-code-completion-not-working/

Regards,

M.Y. Developers

#11

Hello Everyone,

Please try the new Glider 1.9.08. There is be much better multi-file integration in this version. Please let us know how it works out for you. The upgrade is free and the trial keys are reset so you can try it out again if you wish.

Regards,

M.Y. Developers

#12

Version 1.9 fixes the issue. Thanks. On a side note is there a way to activate autocomplete without having to hit control + space?  

#13

Hello Quantum,

Here you go:

http://forums.coronalabs.com/topic/34907-19-auto-code-completion-not-working/

Regards,

M.Y. Developers