| No initial ValidationJob [message #670285] |
Fri, 13 May 2011 07:01  |
Eclipse User |
|
|
|
Hi
When an Xtext editor starts, there is no invocation of the
ValidationJob, so the editor displays whatever historical problem
markers may exist. These may be very wrong. After a dummy edit the
ValidationJob runs and all is sensible.
I recall a Bugzilla response a while ago, when I understood less about
Xtext, that this was intended behaviour and matched JDT.
I don't think it does. Is it really correct for the initial editor
display to be so wrong?
(I do not have the Xtext nature and so builder active.)
Regards
Ed Willink
|
|
|
|
| Re: No initial ValidationJob [message #670291 is a reply to message #670287] |
Fri, 13 May 2011 07:44  |
| Eclipse User |
|
|
|
Hi Sebastian
Thanks; works beautifully.
[For anyone else reading: bind ValidatingEditorCallback as
IXtextEditorCallback.]
Regards
Ed
On 13/05/2011 12:20, Sebastian Zarnekow wrote:
> Hi Ed,
>
> you can bind the ValidatingEditorCallback for your language. It is
> meant to be used for languages that do not use the builder
> infrastructure. In any other case, the markers should be in sync with
> the file's content as long as you do not change your validation rules.
> That's why we do not trigger an initial validation by default.
>
> Regards,
> Sebastian
|
|
|
Powered by
FUDForum. Page generated in 0.26323 seconds
Home