Skip to content
This repository has been archived by the owner on Apr 3, 2018. It is now read-only.

Content Assist: Invalid location (inside unmodifiable token) #100

Closed
llucenic opened this issue Mar 16, 2015 · 7 comments
Closed

Content Assist: Invalid location (inside unmodifiable token) #100

llucenic opened this issue Mar 16, 2015 · 7 comments

Comments

@llucenic
Copy link

Got this after upgrade to latest release 0.11:

ddt-bug-content-assist

I have used intensively previous two versions of DDT and have not encountered this popup. The problem appears at every dot within the q{ } section.

DDT version: 0.11.0
System: Linux Mint 17.1 64bit

Message: Could not perform content assist: Invalid location (inside unmodifiable token)

Eclipse Error Log - Session Data:
eclipse.buildId=4.4.2.M20150204-1700
java.version=1.7.0_75
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=sk_SK
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product

@bruno-medeiros
Copy link
Contributor

You can't invoke content assist in the middle of .. (between the two dots), since that is the range token. This behavior is exactly the same outside of q{}, and also on DTT version 0.10.4. So perhaps this bug is invalid or not described correctly?
Note that if you are invoking Content Assist and the editor file is not saved, you will stumble across bug #99

@bruno-medeiros
Copy link
Contributor

I've just found a similar but unrelated bug: #101

@llucenic
Copy link
Author

Hi Bruno, sorry for not being precise enough in the depiction. The problem appears, when you press the dot while cursor is beyond "node", not from in between the two dots. The screenshot was taken afterwards. Please reopen this issue, as your reason does not apply in this case.

@bruno-medeiros
Copy link
Contributor

Hum, I think I see the problem now

@bruno-medeiros
Copy link
Contributor

So, is the problem that content assist fails with that error anywhere inside a q{ } token string?

@bruno-medeiros
Copy link
Contributor

If the issue is that an error dialog appears, instead of the content assist simply not opening, that's #102
If the issue is that one can't perform content assist inside token strings, I've created #107
If it's something else, explain and I'll reopen.

@llucenic
Copy link
Author

llucenic commented Apr 3, 2015

The issue #107 seems to be it for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants