Greyed out validation markers in Designer #2190
Comments
|
The items list in the lower left of the designer window also is not populated with items. Could this be another symptom of the above problem? |
|
Yes, other symptom of the same root cause. |
|
I'm also not having any of my Items identified in my Rules. Actions are also not recognized in Rules (below is a screenshot showing createTimer and logInfo . Hovering over the error it says "The method logInfo(String, String) is undefined".
|
|
I installed yesterday the latest snapshot of the designer - and my rules look pretty much like the image posted by rkoshak. @kaikreuzer , since this seems to be an open issue for quite a while now, and Highlightig/Check/TypeAread are the only reasons to use the Designer, can i conclude this part of the project to be dead? Since more and more functionality moves into the GUI, i would understand that, I'm just curious.... |
|
@kohlsalem I would love to see this fixed myself, but I don't know how to do it (at least without spending quite some amount of time, which I simply do not have) and nobody else came up with a fix yet either. So please help finding people that are deep in Eclipse RCP and Xtext and that are willing to give a hand here! |
...in order to fix the registry population with elements. fixes eclipse-archived#2190 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
|
no in-depth Xtext knowledge was needed. Just some unhappy services... |
...in order to fix the registry population with elements. fixes #2190 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
|
Re-opening as I still have issues with the rule resolution:
|
|
Yes, indeed, I can confirm that rules are still awfully broken. Will have a look too. |
...in the dynamically created project. fixes eclipse-archived#2190 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
|
As it turned out there was a package imported twice in they dynamically created project, leading to an invalid manifest which could not resolve any classes except those from the JRE. I have created #2891 in order to prevent this. Could you please check if that solves your issues? |
|
Somewhat related question: How complicated would it be to export what's special about the Designer as an eclipse ide plugin? |
Not entirely. The error markers still appear when opening a rule and are greyed our shortly after. So it's a good step forward, but not yet there.
You mean like #630? To much effort and and it wouldn't solve any concrete issue. |
...in the dynamically created project. fixes #2190 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
|
@SJKA I can confirm that the problems are not entirely solved yet. In the following screenshots you can see the "greyed out error markers" @kaikreuzer was mentioning before. Any chance you could have yet another look? Thanks ;)
|
...in order to fix the registry population with elements. fixes eclipse-archived#2190 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
...in the dynamically created project. fixes eclipse-archived#2190 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
|
I just had another look at it (sorry it fell off my desk...). I think I figured out the reason for the greyed out markers: The script and model runtimes trigger another validation, interfering with the same resources that are displayed in the editors. So while in #2873 the items runtime bundle was necessary to fix the item resolution, the rules and script runtime should not have been added. I will propose a fix for it. |
|
I think we will live with this greyed out validation markers and not put further effort in the designer, see https://dev.eclipse.org/mhonarc/lists/smarthome-dev/msg00146.html. |
kaikreuzer
changed the title
Items are not resolved in the Designer, i.e. when trying to use content completion e.g. in sitemaps, no proposals show up.
The text was updated successfully, but these errors were encountered: