[ecodiv]

Added exception handling for specific modules in gconsole.py to avoid that the GUI console automatically applies a color table to the output, thereby overwriting the intended RGB colors.

An attempt to solve the issue reported in #6826. I applied the patch, and for me, it seems to work.

[petrasovaa]

This is misunderstood. r.mapcalc is not exempt, it just required different parsing than all other tools. The only change here that makes sense is fixing the errors, indeed, KeyError seems wrong.

[petrasovaa]

@ecodiv the changing of the color table should happen only if you have it in the settings (Layers - Default raster settings), please make sure it's not checked. If the problem persists, I would need to look into it more.
We could decide some tools should be exempt from this, but the change would have to look differently. I think this feature, if we even want it, should be implemented in some other way, currently it's hardcoded in the C library.

[ecodiv]

Thanks for the feedback. I'll have a look at my settings. But I think irrespective of the setting, this module should be exempted because it never makes sense, the whole purpose of that module is to define a very specific color table.

[ecodiv]

@ecodiv the changing of the color table should happen only if you have it in the settings (Layers - Default raster settings), please make sure it's not checked. If the problem persists, I would need to look into it more. We could decide some tools should be exempt from this, but the change would have to look differently. I think this feature, if we even want it, should be implemented in some other way, currently it's hardcoded in the C library.

@petrasovaa The default color table is unchecked. But I just ran mapcalc, and the outcome got automatically assigned the viridis color table. (grass 8.6dev on Linux)

[petrasovaa]

@petrasovaa The default color table is unchecked. But I just ran mapcalc, and the outcome got automatically assigned the viridis color table. (grass 8.6dev on Linux)

Viridis is the default, so I guess I don't understand what is the problem?

[ecodiv]

@petrasovaa The default color table is unchecked. But I just ran mapcalc, and the outcome got automatically assigned the viridis color table. (grass 8.6dev on Linux)

Viridis is the default, so I guess I don't understand what is the problem?

You're right, sorry for the noise.

[ecodiv]

@ecodiv the changing of the color table should happen only if you have it in the settings (Layers - Default raster settings), please make sure it's not checked. If the problem persists, I would need to look into it more. We could decide some tools should be exempt from this, but the change would have to look differently. I think this feature, if we even want it, should be implemented in some other way, currently it's hardcoded in the C library.

Do you have any ideas how to deal with modules that create output rasters that should not get assigned a color table? In the current situation, r.shade isn't useful.

[petrasovaa]

From this PR I isolated the error fix unrelated to the issue.

[petrasovaa]

I suggest to further discuss the topic in the issue, this PR with the little exception fix will get merged.