##class( autocomplete for classnames

Question

Question

Mathew Lambert · May 23, 2018

#Development Environment

In Studio whenever you write ##class( and then you start writing it will autocomplete the classname.

I can't find how to do that in atelier.

Discussion (8)0

Log in or sign up to continue

Joyce Zhang · May 23, 2018

Hi Mathew,

As @Erez Even Paz suggested, when you type the content assist keystrokes, CTRL+Space, the editor opens a pop-up box listing possible completions. With a large codebase, it takes longer to index prior to cache existing, and that is why you encountered the performance hit. @Scott Morrison @Fred Gustafsson, thank you for bringing this issue to our attention. You can rest assured that the development team will prioritize it and we will keep you informed.

Best,
Joyce

0 0

score 0 · Answer 1 · 2018-05-23T03:53:55-04:00

Erez Even Paz · May 23, 2018

try Ctrl + Space whenever you want the autocomplete to appear :)

0 0

score 0 · Answer 2 · 2018-05-23T03:57:13-04:00

Already tryed, it stays bloqued some seconds, and then nothing.

I can read on the status tab:

Computation of proposals takes too long. Please try again.

score 0 · Answer 3 · 2018-05-23T08:32:04-04:00

I agree with Scott, it is so slow that is close to useless. I can't see any reason for being this slow, it's just a simple lookup.

score 0 · Answer 4 · 2018-05-23T10:02:56-04:00

Well in my case I even tried with some indications from the documentation about running

set rtn= ##class(%Atelier.v1.Utils.MetaData).Build("DB")

but it didn't solve anything (in fact I don't know how to check if it's taking into account this data generated)

It always gives me the too long error

score 0 · Answer 5 · 2018-05-24T01:30:20-04:00

I can understand that prior to cache it will take longer, but how can I force a cache heat up. Because It's been one week and I'm still getting the error.

score 0 · Answer 6 · 2018-05-23T07:36:25-04:00

I had the same issue when I first started using Eclipse/Atelier, intellisense/autocomplete consistently not working. I'm guessing it was to do with caching of files, as it's gotten better over time. It's still slow to respond. Typically, when I hit dot/period after a class/subclass (Ens.), it's a few seconds before anything comes up.

score 0 · Answer 7 · 2018-05-24T10:20:57-04:00

It probably has to do with the size of your files or projects. We have seen similar issues before, so I'd say contact support for further investigation.