#3603 closed bug (fixed)
r.colors has no effect on GRASS rasters (after the merge of the rasters branch)
| Reported by: | lutra | Owned by: | rblazek |
|---|---|---|---|
| Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
| Component: | Rasters | Version: | Trunk |
| Keywords: | Cc: | pcav | |
| Must Fix for Release: | Yes | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
summary says it all.
Change History (4)
comment:1 by , 13 years ago
follow-up: 4 comment:2 by , 13 years ago
Furthermore, new layers will have a greyscale istead of appropriate color, as it happened before
comment:3 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in r15749.
GRASS provider is now completely reloaded if source data have changed. That introduces another issue: everything set by user in layer properties dialog is lost. There is no simple solution for this, keeping settings done by user could result in other problems, e.g. original data range was 1-100, color table was changed by user but new data range is 100-200.
comment:4 by , 13 years ago
Replying to pcav:
Furthermore, new layers will have a greyscale istead of appropriate color, as it happened before
That is expected, if a data source does not have any color table assigned, QGIS is using grayscale by default, d.rast is using colors by default.
if you remove the raster from TOC and then add it again the new colormap will show ok. The refresh button has no effect. Not very handy.