#2250: d.text unsupported from command line ------------------------+--------------------------------------------------- Reporter: veroandreo | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.1.0 Component: Display | Version: unspecified Keywords: d.text | Platform: Linux Cpu: x86-64 | ------------------------+---------------------------------------------------
Comment(by wenzeslaus): To make it more clear: In command line: {{{ GRASS 7.1.svn (nc_spm_08):~ > d.mon wx0 GRASS 7.1.svn (nc_spm_08):~ > d.rast elevation 100% GRASS 7.1.svn (nc_spm_08):~ > d.text text="Hola" at=30,30 GRASS_INFO_WARNING(3720,1): Unsupported command d.text. GRASS_INFO_END(3720,1) }}} In the main GUI (`g.gui`, wxGUI): {{{ d.rast elevation d.text text="Hola" at=30,30 }}} results in error dialog with: {{{ Command 'd.text' not yet implemented in the WxGUI. Try adding it as a command layer instead. }}} Adding a command layer ("`d.text text="Hola" at=30,30`") works. My first guess is that layers in `d.mon` wxGUI backend are added by standard mechanism, the same as in GUI. While command layers are added separately. The questing is if just adding all layers in `d.mon` wxGUI backend as command layers would solve the problem. Can this be so simple, or are there some consequences? I can see problem with all dependent functions in wxGUI (e.g. profile) which accepts rasters or vectors maps from layers currently loaded into the map display, so there apparently need to know the type of the layer, just command layer is not enough. By the way, I'm actually not sure if you can safely use `d.*` commands with `d.mon wx*` in script (or for loop in command line). This is a topic for different ticket, however. ''Vero, note that you can use `{{{` and `}}}` to add source code listings (verbatim, list of commands) which is simpler and nicer than `[[BR]]`. Generally, you can use Trac WikiFormatting.'' -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2250#comment:1> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev