error stripes

View: New views
6 Messages — Rating Filter:   Alert me  

error stripes

by Bryan Boone :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

RC1/Linux/KDE
When I start resolving error stripes by clicking on the red marks in the
editor, the marks don't update as I add/remove lines.
Seems like if there's real time parsing of source, then the error
stripes ought to update, too.
-Bryan

Re: error stripes

by jiri prox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Bryan,

the error stripes should be always in sync with error annotations in
editor. Can you provide more info about your use case, please?  Exact
steps to reproduce would be welcome.

Thanks
Jirka

Bryan Boone wrote:

> RC1/Linux/KDE
> When I start resolving error stripes by clicking on the red marks in
> the editor, the marks don't update as I add/remove lines.
> Seems like if there's real time parsing of source, then the error
> stripes ought to update, too.
> -Bryan


Re: error stripes

by Bryan Boone :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Just to make sure my terminology is correct, error stripes are in the
right margin of the editor, right?

In my use case, I delete a class member which is accessed in say, 40
place in the source.  As I start at the top (by clicking on the first
red mark) and adding/removing complete lines of code, when I click on
subsequent red marks, the mark doesn't take me to the next error.  It
takes me to where the error was, before I added/removed lines to fix the
previous error.

-Bryan

Jiri Prox wrote:

> Hi Bryan,
>
> the error stripes should be always in sync with error annotations in
> editor. Can you provide more info about your use case, please?  Exact
> steps to reproduce would be welcome.
>
> Thanks
> Jirka
>
> Bryan Boone wrote:
>
>> RC1/Linux/KDE
>> When I start resolving error stripes by clicking on the red marks in
>> the editor, the marks don't update as I add/remove lines.
>> Seems like if there's real time parsing of source, then the error
>> stripes ought to update, too.
>> -Bryan
>

Re: error stripes

by jiri prox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

yes,  the terminology is correct.
I've tried your steps and still cannot reproduce it. Are only errors
shown in the errorstripe or are there another types of marks (versioning
marks, warnings etc..)? Anyway it seems to me as a bug, so please file
an issue, it's importat to have it reported.

Thanks
Jirka

Bryan Boone wrote:

> Just to make sure my terminology is correct, error stripes are in the
> right margin of the editor, right?
>
> In my use case, I delete a class member which is accessed in say, 40
> place in the source.  As I start at the top (by clicking on the first
> red mark) and adding/removing complete lines of code, when I click on
> subsequent red marks, the mark doesn't take me to the next error.  It
> takes me to where the error was, before I added/removed lines to fix
> the previous error.
>
> -Bryan
>
> Jiri Prox wrote:
>
>> Hi Bryan,
>>
>> the error stripes should be always in sync with error annotations in
>> editor. Can you provide more info about your use case, please?  Exact
>> steps to reproduce would be welcome.
>>
>> Thanks
>> Jirka
>>
>> Bryan Boone wrote:
>>
>>> RC1/Linux/KDE
>>> When I start resolving error stripes by clicking on the red marks in
>>> the editor, the marks don't update as I add/remove lines.
>>> Seems like if there's real time parsing of source, then the error
>>> stripes ought to update, too.
>>> -Bryan
>>
>>

Re: error stripes

by Bryan Boone :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'll file it...
It seems to happen only when I delete blocks of code, instead of
correcting a typo.
Things get "fixed" after a recompile of the file (single compile)

-Bryan

Jiri Prox wrote:

> Hi,
>
> yes,  the terminology is correct.
> I've tried your steps and still cannot reproduce it. Are only errors
> shown in the errorstripe or are there another types of marks (versioning
> marks, warnings etc..)? Anyway it seems to me as a bug, so please file
> an issue, it's importat to have it reported.
>
> Thanks
> Jirka
>
> Bryan Boone wrote:
>
>> Just to make sure my terminology is correct, error stripes are in the
>> right margin of the editor, right?
>>
>> In my use case, I delete a class member which is accessed in say, 40
>> place in the source.  As I start at the top (by clicking on the first
>> red mark) and adding/removing complete lines of code, when I click on
>> subsequent red marks, the mark doesn't take me to the next error.  It
>> takes me to where the error was, before I added/removed lines to fix
>> the previous error.
>>
>> -Bryan
>>
>> Jiri Prox wrote:
>>
>>> Hi Bryan,
>>>
>>> the error stripes should be always in sync with error annotations in
>>> editor. Can you provide more info about your use case, please?  Exact
>>> steps to reproduce would be welcome.
>>>
>>> Thanks
>>> Jirka
>>>
>>> Bryan Boone wrote:
>>>
>>>> RC1/Linux/KDE
>>>> When I start resolving error stripes by clicking on the red marks in
>>>> the editor, the marks don't update as I add/remove lines.
>>>> Seems like if there's real time parsing of source, then the error
>>>> stripes ought to update, too.
>>>> -Bryan
>>>

Re: error stripes

by Bryan Boone :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

http://www.netbeans.org/issues/show_bug.cgi?id=122978

Bryan Boone wrote:

> I'll file it...
> It seems to happen only when I delete blocks of code, instead of
> correcting a typo.
> Things get "fixed" after a recompile of the file (single compile)
>
> -Bryan
>
> Jiri Prox wrote:
>> Hi,
>>
>> yes,  the terminology is correct.
>> I've tried your steps and still cannot reproduce it. Are only errors
>> shown in the errorstripe or are there another types of marks (versioning
>> marks, warnings etc..)? Anyway it seems to me as a bug, so please file
>> an issue, it's importat to have it reported.
>>
>> Thanks
>> Jirka
>>
>> Bryan Boone wrote:
>>
>>> Just to make sure my terminology is correct, error stripes are in the
>>> right margin of the editor, right?
>>>
>>> In my use case, I delete a class member which is accessed in say, 40
>>> place in the source.  As I start at the top (by clicking on the first
>>> red mark) and adding/removing complete lines of code, when I click on
>>> subsequent red marks, the mark doesn't take me to the next error.  It
>>> takes me to where the error was, before I added/removed lines to fix
>>> the previous error.
>>>
>>> -Bryan
>>>
>>> Jiri Prox wrote:
>>>
>>>> Hi Bryan,
>>>>
>>>> the error stripes should be always in sync with error annotations in
>>>> editor. Can you provide more info about your use case, please?  Exact
>>>> steps to reproduce would be welcome.
>>>>
>>>> Thanks
>>>> Jirka
>>>>
>>>> Bryan Boone wrote:
>>>>
>>>>> RC1/Linux/KDE
>>>>> When I start resolving error stripes by clicking on the red marks in
>>>>> the editor, the marks don't update as I add/remove lines.
>>>>> Seems like if there's real time parsing of source, then the error
>>>>> stripes ought to update, too.
>>>>> -Bryan
LightInTheBox - Buy quality products at wholesale price