Really annoying exception for the last 4 eaps

http://www.intellij.net/tracker/idea/viewSCR?publicId=45590 This just
happened again in the latest eap. I've been getting this problem for
the last 4 eaps. Can someone please fix it? It happens when I hit
enter after a line defining a variable in the class... I hit enter and I
end up with xxx on the next line and an exception is thrown. It happens
so much that I can't even stay in Irida long enough out of frustration!

Thanks

R

5 comments
Comment actions Permalink

Yes that happens to me all the time too! indeed very annoying...but I
guess that's how life is living on the edge ;)

Robert S. Sfeir wrote:

http://www.intellij.net/tracker/idea/viewSCR?publicId=45590 This just
happened again in the latest eap. I've been getting this problem for
the last 4 eaps. Can someone please fix it? It happens when I hit
enter after a line defining a variable in the class... I hit enter and I
end up with xxx on the next line and an exception is thrown. It happens
so much that I can't even stay in Irida long enough out of frustration!

Thanks

R

0
Comment actions Permalink

I third that motion.

Arik Kfir wrote:

Yes that happens to me all the time too! indeed very annoying...but I
guess that's how life is living on the edge ;)

>

Robert S. Sfeir wrote:

>
>> http://www.intellij.net/tracker/idea/viewSCR?publicId=45590 This
>> just happened again in the latest eap. I've been getting this
>> problem for the last 4 eaps. Can someone please fix it? It happens
>> when I hit enter after a line defining a variable in the class... I
>> hit enter and I end up with xxx on the next line and an exception is
>> thrown. It happens so much that I can't even stay in Irida long
>> enough out of frustration!
>>
>> Thanks
>>
>> R
>

0
Comment actions Permalink

I also get this all the time and have submitted the exception via the auto error reporting many times.

VERY ANNOYING!

A quick search in tracker shows the first reference to "Should not be called on Chameleons" on Feb 13. It has been reported at least 31 times and every report is still in the "Submitted" state.

It should definitely be fixed ASAP.

0
Comment actions Permalink

Tim Haley wrote:

I also get this all the time and have submitted the exception via the auto error reporting many times.

VERY ANNOYING!

A quick search in tracker shows the first reference to "Should not be called on Chameleons" on Feb 13. It has been reported at least 31 times and every report is still in the "Submitted" state.

It should definitely be fixed ASAP.

as annoying as it gets - I'm sure the development guys have a lot on
their mind, and are aware of it.

Give'em time! ;)

0
Comment actions Permalink

In article <d3ejnj$8m6$1@is.intellij.net>,
Arik Kfir <arikkfir@users.sourceforge.net> wrote:

Tim Haley wrote:

I also get this all the time and have submitted the exception via the auto
error reporting many times.

VERY ANNOYING!

A quick search in tracker shows the first reference to "Should not be
called on Chameleons" on Feb 13. It has been reported at least 31 times
and every report is still in the "Submitted" state.

It should definitely be fixed ASAP.

as annoying as it gets - I'm sure the development guys have a lot on
their mind, and are aware of it.

Give'em time! ;)


I think there should be something that raises exceptions up the priority
list, especially if it's been reported 37 times like this one has.

R

0

Please sign in to leave a comment.