Active row should highlight

Bug #419009 reported by Ken McLean
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenScore
Fix Released
Wishlist
Craig Mahony

Bug Description

Active row should highlight

Revision history for this message
Craig Mahony (cmahony) wrote :

Yes I can make the active row highlighted. But that means no cell color coding in that row! Which do we want as we cannot have both?

Revision history for this message
Tudor Holton (tudor) wrote : Re: [Bug 419009] Re: Active row should highlight

I had a bit more of a think about this.

Since we have colors already for the heat, we know when there are errors
and where to look for them.

Having an extra column to the left that contains a colored square in
place of the entire row colored would allow us two more things:
1) We'd be able to highlight the active row as requested.
2) We'd be able to highlight field errors as distinct from line errors.

Obviously this would be a larger change, and we should consider the
effect this will have on the user. I think for the most part, the error
highlighting when it's not the active row is too strong. We need to
reduce the palette a bit to distinguish between errors that just
happened and errors that happened in earlier data entry.

Craig Mahony wrote:
> Yes I can make the active row highlighted. But that means no cell color
> coding in that row! Which do we want as we cannot have both?
>
>

Revision history for this message
Craig Mahony (cmahony) wrote :

If i am interpreting this correctly, we would then put the blue errrs(team
errors) in the left empty column. Have the left empty cell of the row be
"grey"? to represent selection and have the red and yellow warnings for cell
warnings?

Do I have this correct?

Having an empty left row allows me to more easily(?) allow multilpe row
selection and then deletion as well.

craig

----- Original Message -----
From: "Tudor Holton" <email address hidden>
To: <email address hidden>
Sent: Tuesday, September 01, 2009 6:49 PM
Subject: Re: [Bug 419009] Re: Active row should highlight

I had a bit more of a think about this.

Since we have colors already for the heat, we know when there are errors
and where to look for them.

Having an extra column to the left that contains a colored square in
place of the entire row colored would allow us two more things:
1) We'd be able to highlight the active row as requested.
2) We'd be able to highlight field errors as distinct from line errors.

Obviously this would be a larger change, and we should consider the
effect this will have on the user. I think for the most part, the error
highlighting when it's not the active row is too strong. We need to
reduce the palette a bit to distinguish between errors that just
happened and errors that happened in earlier data entry.

Craig Mahony wrote:
> Yes I can make the active row highlighted. But that means no cell color
> coding in that row! Which do we want as we cannot have both?
>
>

--
Active row should highlight
https://bugs.launchpad.net/bugs/419009
You received this bug notification because you are a bug assignee.

Status in OpenScore: New

Bug description:
Active row should highlight

Revision history for this message
Tudor Holton (tudor) wrote :

Close. Selection would highlight the entire row not just the first
column. The only thing signalled in the left hand empty column would be
for line errors.

Craig Mahony wrote:
> If i am interpreting this correctly, we would then put the blue errrs(team
> errors) in the left empty column. Have the left empty cell of the row be
> "grey"? to represent selection and have the red and yellow warnings for cell
> warnings?
>
> Do I have this correct?
>
> Having an empty left row allows me to more easily(?) allow multilpe row
> selection and then deletion as well.
>
> craig
>
> ----- Original Message -----
> From: "Tudor Holton" <email address hidden>
> To: <email address hidden>
> Sent: Tuesday, September 01, 2009 6:49 PM
> Subject: Re: [Bug 419009] Re: Active row should highlight
>
>
> I had a bit more of a think about this.
>
> Since we have colors already for the heat, we know when there are errors
> and where to look for them.
>
> Having an extra column to the left that contains a colored square in
> place of the entire row colored would allow us two more things:
> 1) We'd be able to highlight the active row as requested.
> 2) We'd be able to highlight field errors as distinct from line errors.
>
> Obviously this would be a larger change, and we should consider the
> effect this will have on the user. I think for the most part, the error
> highlighting when it's not the active row is too strong. We need to
> reduce the palette a bit to distinguish between errors that just
> happened and errors that happened in earlier data entry.
>
> Craig Mahony wrote:
>
>> Yes I can make the active row highlighted. But that means no cell color
>> coding in that row! Which do we want as we cannot have both?
>>
>>
>>
>
>

Revision history for this message
Craig Mahony (cmahony) wrote :

This is still a problem. If a line is selected then the fields cannot be
color coded for individual filed errors, eg not eligible for constraint

Craig
----- Original Message -----
From: "Tudor Holton" <email address hidden>
To: <email address hidden>
Sent: Wednesday, September 02, 2009 10:40 PM
Subject: Re: [Bug 419009] Re: Active row should highlight

Close. Selection would highlight the entire row not just the first
column. The only thing signalled in the left hand empty column would be
for line errors.

Craig Mahony wrote:
> If i am interpreting this correctly, we would then put the blue errrs(team
> errors) in the left empty column. Have the left empty cell of the row be
> "grey"? to represent selection and have the red and yellow warnings for
> cell
> warnings?
>
> Do I have this correct?
>
> Having an empty left row allows me to more easily(?) allow multilpe row
> selection and then deletion as well.
>
> craig
>
> ----- Original Message -----
> From: "Tudor Holton" <email address hidden>
> To: <email address hidden>
> Sent: Tuesday, September 01, 2009 6:49 PM
> Subject: Re: [Bug 419009] Re: Active row should highlight
>
>
> I had a bit more of a think about this.
>
> Since we have colors already for the heat, we know when there are errors
> and where to look for them.
>
> Having an extra column to the left that contains a colored square in
> place of the entire row colored would allow us two more things:
> 1) We'd be able to highlight the active row as requested.
> 2) We'd be able to highlight field errors as distinct from line errors.
>
> Obviously this would be a larger change, and we should consider the
> effect this will have on the user. I think for the most part, the error
> highlighting when it's not the active row is too strong. We need to
> reduce the palette a bit to distinguish between errors that just
> happened and errors that happened in earlier data entry.
>
> Craig Mahony wrote:
>
>> Yes I can make the active row highlighted. But that means no cell color
>> coding in that row! Which do we want as we cannot have both?
>>
>>
>>
>
>

--
Active row should highlight
https://bugs.launchpad.net/bugs/419009
You received this bug notification because you are a bug assignee.

Status in OpenScore: New

Bug description:
Active row should highlight

Revision history for this message
Tudor Holton (tudor) wrote :

This happens already but just not for highlighting.

At least you'd see the errors underneath when the line wasn't highlighted.

Craig Mahony wrote:
> This is still a problem. If a line is selected then the fields cannot be
> color coded for individual filed errors, eg not eligible for constraint
>
> Craig
> ----- Original Message -----
> From: "Tudor Holton" <email address hidden>
> To: <email address hidden>
> Sent: Wednesday, September 02, 2009 10:40 PM
> Subject: Re: [Bug 419009] Re: Active row should highlight
>
>
> Close. Selection would highlight the entire row not just the first
> column. The only thing signalled in the left hand empty column would be
> for line errors.
>
> Craig Mahony wrote:
>
>> If i am interpreting this correctly, we would then put the blue errrs(team
>> errors) in the left empty column. Have the left empty cell of the row be
>> "grey"? to represent selection and have the red and yellow warnings for
>> cell
>> warnings?
>>
>> Do I have this correct?
>>
>> Having an empty left row allows me to more easily(?) allow multilpe row
>> selection and then deletion as well.
>>
>> craig
>>
>> ----- Original Message -----
>> From: "Tudor Holton" <email address hidden>
>> To: <email address hidden>
>> Sent: Tuesday, September 01, 2009 6:49 PM
>> Subject: Re: [Bug 419009] Re: Active row should highlight
>>
>>
>> I had a bit more of a think about this.
>>
>> Since we have colors already for the heat, we know when there are errors
>> and where to look for them.
>>
>> Having an extra column to the left that contains a colored square in
>> place of the entire row colored would allow us two more things:
>> 1) We'd be able to highlight the active row as requested.
>> 2) We'd be able to highlight field errors as distinct from line errors.
>>
>> Obviously this would be a larger change, and we should consider the
>> effect this will have on the user. I think for the most part, the error
>> highlighting when it's not the active row is too strong. We need to
>> reduce the palette a bit to distinguish between errors that just
>> happened and errors that happened in earlier data entry.
>>
>> Craig Mahony wrote:
>>
>>
>>> Yes I can make the active row highlighted. But that means no cell color
>>> coding in that row! Which do we want as we cannot have both?
>>>
>>>
>>>
>>>
>>
>
>

Revision history for this message
Craig Mahony (cmahony) wrote :

The active row is now highlighted. However, I have not implemented the empty left column that shows line errors because I do not believe it is necessary. The line errors will show anyway. First in te statusbar and errorpanel, then in the row after the user moves to the next row.

Changed in openscore:
status: New → Fix Committed
Ken McLean (kenmclean)
Changed in openscore:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.