> > In those cases, there are comments right before the loops explaining
> what's
> > going on, and they're just scanning loops (used to position an int
> > variable). Can you suggest a different phrasing so we can see the
> options?
> Very simple ... instead of the ";", use an empty { } ... ok, minimal
> but at least the warnings are gone.
> Ok ?
>
Yep. You want me to make the change or you?
>
> > I'd make the SortIndicatorImage class protected instead.
> private (they are already protected) ...
>
No, the fields are protected, and the class is private, which is what is
generating the warning. If the class were protected as well as the fields,
all would be well :)
