Bug report #3603

r.colors has no effect on GRASS rasters (after the merge of the rasters branch)

Added by Giovanni Manghi over 9 years ago. Updated over 9 years ago.

Status:Closed
Priority:Low
Assignee:Redmine Admin
Category:Rasters
Affected QGIS version: Regression?:No
Operating System:All Easy fix?:No
Pull Request or Patch supplied: Resolution:fixed
Crashes QGIS or corrupts data: Copied to github as #:13662

Description

summary says it all.

History

#1 Updated by Giovanni Manghi over 9 years ago

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.

#2 Updated by Paolo Cavallini over 9 years ago

Furthermore, new layers will have a greyscale istead of appropriate color, as it happened before

#3 Updated by Redmine Admin over 9 years ago

  • Resolution set to fixed
  • Status changed from Open to Closed

Fixed in d7d7caf4 (SVN r15750).

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.

#4 Updated by Redmine Admin over 9 years ago

Replying to [comment:2 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.

Also available in: Atom PDF