Box displaying exceptions...

The box is there so that you can report the exceptions.
If you are intimidated by it, why don't you just wait for the final release?!
The EAP is not mainly for you to work more productively than with the last release, but for JetBrains to gather feedback.

That said, the latest EAPs really through way too much exceptions...

Stephen Kelvin wrote:

The box is there so that you can report the exceptions.
If you are intimidated by it, why don't you just wait for the final release?!
The EAP is not mainly for you to work more productively than with the last release, but for JetBrains to gather feedback.

That said, the latest EAPs really through way too much exceptions...

Well, of course I know, that I use an EAP build...
But why should every single exception interrupt my work? I think it
would be enought to just display that red sign (and leave the focus
where it is)...

But maybe "disruption" is a feature ;)



Johannes Schneider

Well,

one more point: What do u think about a button that recreates the
PSI-document for the active editor? I often have to reopen the actual
project, because the internal model is in a "funny" state and throwing
many, many Exceptions...

This would be a great time saver. Also could help to avoid consecutive
exceptions due to illegal state of PSI representation.


Johannes Schneider

Ok, I did not read carefully enough.
It seems that the problem you describe is part of the infamous "Stealing focus" problem that has been discussed to great length and then again much longer in other forum posts.

For me the 'red box' never takes away the focus (on Windows).

Maybe even do it automatically when an exception occurs?

Good way to wind up in an eternal throw/rethrow loop.

Patrik Andersson wrote:

Good way to wind up in an eternal throw/rethrow loop.

Maybe not the automatic recreation of the PSI-document, for your reason exactly, but the
button is a great idea.
A button to clear the cache would also be very useful during EAP.
If they are placed on the exception reporting dialog, they would not affect the final
release either.

one more point: What do u think about a button that
recreates the
PSI-document for the active editor?

Every now and then someone proposes that IDEA should have a way around some exceptions: recreate a PSI document, clear caches, reload project, or any other action that is known to temporarily fix an exception.

People, the exceptions are there for a reason: if an exception was throw, IDEA is in a stat it shouldn't have been. It should not work around this exception, but prevent it from happening in the first place. I know, it sucks to get an exception, report it, and then keep getting it again in the following days -- but that's life for an EAP member.

Marcus Brito wrote:
>>one more point: What do u think about a button that
>>recreates the
>>PSI-document for the active editor?

Every now and then someone proposes that IDEA should have a way around some exceptions: recreate a PSI document, clear caches, reload project, or any other action that is known to temporarily fix an exception.

People, the exceptions are there for a reason: if an exception was throw, IDEA is in a stat it shouldn't have been. It should not work around this exception, but prevent it from happening in the first place. I know, it sucks to get an exception, report it, and then keep getting it again in the following days -- but that's life for an EAP member.

Maybe as an incentive to report the issue, the feedback tool should recreate the PSI
document, clear caches, reload project, or whatever immediately after the issue is reported.
The problem isn't reporting the issue, it is getting back into a usable state to continue
participating in the EAP once an error occurs.