Code inspections

Why is the "Run" button on my Code Inspection dialog always grayed out? How
do I inspect code?? The help is unhelpful in this case. There's no obvious
reason, or notification, of why code inspections are unavailable. Help?


10 comments
Comment actions Permalink

I found that you have to have the very top check-box checked in order to run
code inspections. Huh?

Since this box defaults to unchecked, is this a known bug?

"Paul Bradshaw" <pbradshaw@vignette.com> wrote in message
news:bv9edj$ujo$1@is.intellij.net...

Why is the "Run" button on my Code Inspection dialog always grayed out?

How

do I inspect code?? The help is unhelpful in this case. There's no

obvious

reason, or notification, of why code inspections are unavailable. Help?

>
>


0
Comment actions Permalink

On 1/29/04 2:09 AM, in article bv9ffm$5lj$1@is.intellij.net, "Paul Bradshaw"
<pbradshaw@vignette.com> wrote:

I found that you have to have the very top check-box checked in order to run
code inspections. Huh?

Since this box defaults to unchecked, is this a known bug?

"Paul Bradshaw" <pbradshaw@vignette.com> wrote in message
news:bv9edj$ujo$1@is.intellij.net...

>> Why is the "Run" button on my Code Inspection dialog always grayed out?

How

>> do I inspect code?? The help is unhelpful in this case. There's no

obvious

>> reason, or notification, of why code inspections are unavailable. Help?
>>
>>



As the matter of fact you should have at least one inspection selected to be
able to run. Does it seem like a bug?

--
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Yes, because there are all thsoe other check marks there, and I cannot
understand why THOSE aren't good enough. If you're saying those check marks
dont' actually mean anything (i.e. don't actually select any inspections)
then why are they there? The display is very confusing. The top "node" of
each section has a check mark in it, and it seems that should be sufficient.
It's like the display is either completely lying to me (implying there are a
bunch of inspections selected when in fact there are not) or it's just a
completely counter-intuitive display.

I've just really begun using this latest build in my daily routine, and I'm
finding a lot of really counter-intuitive and confusing displays like this.
I'll post the others in a separate thread. But yes, I think this is just
broken, as is. Either all the check boxes should be cleared, or those
checks that are there should be meaningful and actually do something. It
took me forever to figure out how to get the "run" button to enable.


"Maxim Shafirov (JetBrains)" <max@intellij.com> wrote in message
news:BC3EC0DD.475A%max@intellij.com...

On 1/29/04 2:09 AM, in article bv9ffm$5lj$1@is.intellij.net, "Paul

Bradshaw"

<pbradshaw@vignette.com> wrote:

>

I found that you have to have the very top check-box checked in order to

run

code inspections. Huh?

>

Since this box defaults to unchecked, is this a known bug?

>

"Paul Bradshaw" <pbradshaw@vignette.com> wrote in message
news:bv9edj$ujo$1@is.intellij.net...

>> Why is the "Run" button on my Code Inspection dialog always grayed out?

How

>> do I inspect code?? The help is unhelpful in this case. There's no

obvious

>> reason, or notification, of why code inspections are unavailable.

Help?

>>
>>
>
>

>

As the matter of fact you should have at least one inspection selected to

be

able to run. Does it seem like a bug?

>

--
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>


0
Comment actions Permalink

Yeah, I never understood why toplevel nodes had checkboxes when they didn't do anything, either.

0
Comment actions Permalink

I think these top-level nodes must have a three-state checkbox, like in the installation programs when you select components:
- if none of the subnodes are selected, the group checkbox is blank;
- if all subnodes are selected, the group checkbox is also selected;
- if some of the subnodes are selected, then the group checkbox is in an "indeterminate" state, i.e. selected, but gray.

Does it make more sense?

0
Comment actions Permalink

On 1/30/04 12:11 PM, in article
14671852.1075453899839.JavaMail.itn@is.intellij.net, "Sergei S. Ivanov"
<no_mail@jetbrains.com> wrote:

I think these top-level nodes must have a three-state checkbox, like in the
installation programs when you select components:
- if none of the subnodes are selected, the group checkbox is blank;
- if all subnodes are selected, the group checkbox is also selected;
- if some of the subnodes are selected, then the group checkbox is in an
"indeterminate" state, i.e. selected, but gray.

Does it make more sense?

Right now unchecking group checkbox toggles all underlying inspection off
and checking turns them all back on.
--
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I think these top-level nodes must have a

three-state checkbox, like in the

installation programs when you select components:
- if none of the subnodes are selected, the group

checkbox is blank;

- if all subnodes are selected, the group checkbox

is also selected;

- if some of the subnodes are selected, then the

group checkbox is in an

"indeterminate" state, i.e. selected, but gray.

Does it make more sense?

>

Right now unchecking group checkbox toggles all
underlying inspection off
and checking turns them all back on.


That's right and does not raise any objections. The point is that it should work the other way round, too. I mean, the state of the group checkbox must be consistent with the state of child checkboxes, and selection/deselection of child check boxes must change the state of the group checkbox accordingly. The current initial state when the group checkbox is selected, but all of the child checkboxes are deselected - is totally inconsistent.

0
Comment actions Permalink

On 1/30/04 6:37 PM, in article
21671751.1075477069659.JavaMail.itn@is.intellij.net, "Sergei S. Ivanov"
<no_mail@jetbrains.com> wrote:

>>> I think these top-level nodes must have a
>> three-state checkbox, like in the
>>> installation programs when you select components:
>>> - if none of the subnodes are selected, the group
>> checkbox is blank;
>>> - if all subnodes are selected, the group checkbox
>> is also selected;
>>> - if some of the subnodes are selected, then the
>> group checkbox is in an
>>> "indeterminate" state, i.e. selected, but gray.
>>>
>>> Does it make more sense?
>>
>> Right now unchecking group checkbox toggles all
>> underlying inspection off
>> and checking turns them all back on.


That's right and does not raise any objections. The point is that it should
work the other way round, too. I mean, the state of the group checkbox must be
consistent with the state of child checkboxes, and selection/deselection of
child check boxes must change the state of the group checkbox accordingly. The
current initial state when the group checkbox is selected, but all of the
child checkboxes are deselected - is totally inconsistent.


Finally I see what one means. It's just default blank state in problem. To
be fixed soon.
--
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I think you're missing the point. When NO check-boxes are checked under
them, the top level boxes default to being CHECKED. This is really
confusing, and is a bug that needs to be fixed. If all the boxes below are
unchecked, the top level box should be unchecked. This is upon first
display. I notice if I uncheck all the top level boxes, and then "save" the
state, all the top level boxes instantly become checked again -- even though
there isn't anything checked under them.

Do you understand the problem now?

"Maxim Shafirov (JetBrains)" <max@intellij.com> wrote in message
news:BC400887.48F3%max@intellij.com...

On 1/30/04 12:11 PM, in article
14671852.1075453899839.JavaMail.itn@is.intellij.net, "Sergei S. Ivanov"
<no_mail@jetbrains.com> wrote:

>

I think these top-level nodes must have a three-state checkbox, like in

the

installation programs when you select components:
- if none of the subnodes are selected, the group checkbox is blank;
- if all subnodes are selected, the group checkbox is also selected;
- if some of the subnodes are selected, then the group checkbox is in an
"indeterminate" state, i.e. selected, but gray.

>

Does it make more sense?

Right now unchecking group checkbox toggles all underlying inspection off
and checking turns them all back on.
--
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>


0
Comment actions Permalink

On 1/30/04 8:56 PM, in article bve5ri$mn2$1@is.intellij.net, "Paul Bradshaw"
<pbradshaw@vignette.com> wrote:

I think you're missing the point. When NO check-boxes are checked under
them, the top level boxes default to being CHECKED. This is really
confusing, and is a bug that needs to be fixed. If all the boxes below are
unchecked, the top level box should be unchecked. This is upon first
display. I notice if I uncheck all the top level boxes, and then "save" the
state, all the top level boxes instantly become checked again -- even though
there isn't anything checked under them.

Do you understand the problem now?

Yes I do. Fixed in 1131.

--
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.