After I've specified the grammar using Xtext, I am trying to provide scoping rules. While the validation works in the model (in my example finite state machine, for instance), meaning that when out-of-scope entries are present, the name gets red-underlined; however, my auto-completion does not work. This means that the option ctrl+space seems not to check the code I provide for the specific name. Am I missing some important setting in order to allow for the auto-completion to work? (What is strange is that the validation works).
I'm falling in the same issue... (I would expect a sub-object feature to be invoked by xtext proposals, but this is only the parent object's feature that is processed by the proposal provider...)
What would you suggest ?
A> modify my grammar so that the proposal provider will not fall in this issue. Could you give some hints to follow for improving the grammar ?
B> or somehow adapt the parent ContentAssistContext to a child one with adapted child proposals ? (but I'm not sure of the feasability...)
In advance, thanks for your valuable support !
While implementing a complete example for you, I saw that the completion worked in some cases. Digging further, I saw an InfiniteRecursion exception was thrown while computing possible followElements, and finally convinced myself that I had finally to cope with my old LL-backtracking exceptions I was used to live with ;-)
And it solved my completion problem !
Thanks for Xtext, it is a wonderful tool...