Bug #494
different colors for different kinds of error reports
| Status: | New | Start: | 09/24/2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | V0.15 | |||
| Resolution: |
Description
When a marker has a problem, it shows in the righthand pane in red. This is true whether the problem is an encoding problem or a structural problem.
It would be really nice if there were one color for encoding issues and a different color for structural issues. This would make it possible to focus on one and ignore the other for a time.
(This issue is different from #190, where the user wants to choose what color and size each marker shows as, based on the marker itself.)
Related issues
| related to Feature #190: Color markers | New | 02/26/2009 | ||
| related to Bug #256: Make inferred markers that are in error red rather than b... | Closed | 06/09/2009 | ||
| related to Bug #552: Solid seems to dislike upper ascii data | New |
History
Updated by Cambell Prince over 2 years ago
- Priority changed from Normal to High
- Target version set to V0.11
Updated by Cambell Prince over 2 years ago
- Target version changed from V0.11 to V0.15
Updated by J C almost 2 years ago
I agree that this is an issue. But I think the solution is to only ever color the marker red for structural errors. Encoding issues could be indicated by turning the data itself (to the right of the marker) maroon or a nicely readable dark red.
Also, I suppose this is probably a separate bug, but it is very confusing when working with pre-unicode data that every field that uses the legacy font shows up in red. It gets flagged as an problem due to "upper ASCII data". I'm not sure why, however, since the box "Data for this marker is Unicode enabled" is not checked for any of the fields. Probably a bug.
Finally, please note that the following color-coding issue should probably be fixed at the same time. It should be a quick and easy fixː
http://projects.palaso.org/issues/256 "Make inferred markers that are in error red rather than blue."
Updated by J C almost 2 years ago
It might be helpful if I explained a bit more. Thus far, only the marker has been colored:
blue for inferred,
red for a structural error, or
red for a possible encoding issue.
The original suggestion here was to change the third color. But a marker can't easily be two colors at once, which is why I asked that the data itself (to the right of the marker) be the part that's colored for encoding errors. This way a field that has both a structural error and an encoding error would have a red marker and also maroon (or whatever color) data following the marker.