Re: [GRASS-dev] attribute table manager; SQL Builder; SQL statement is not valid.

[Margherita Di Leo]

Hi,

thank you Maris.
Would it be possible to grey out the "verify" and "apply" buttons before
the comparison operator has been selected? This would be more intuitive.

Thanks
madi

On Tue, Jan 22, 2013 at 7:55 AM, Maris Nartiss  wrote:

> Hi,
> before pressing "Verify", You must enter comparison operator. = or LIKE
>
> Maris.
>
> 2013/1/21 Margherita Di Leo :
> > Hi,
> >
> > I'm using GRASS 6.4.3svn on Red Hat. Trying to use the SQL Builder, I
> always
> > obtain Syntax Error on queries which are self built by the builder...
> > Example on NC dataset:
> > map: census_wake2000
> > I open the attribute table manager from the GUI
> > I select: SQL Query: Advanced
> > Columns: TRT2000 -> Get sample -> Value: 050100 (the first on the top) ->
> > Verify
> > I get:
> >
> > SQL statement is not valid.
> >
> > DBMI-DBF driver error:
> > SQL parser error: syntax error, unexpected STRING processing ''050100' '
> > in statement:
> > SELECT * FROM census_wake2000 WHERE TRT2000 '050100'
> > Error in db_open_select_cursor()
> >
> > ?
> >
> > Thanks,
> > madi
> >
> > --
> > Margherita DI LEO
> > Postdoctoral Researcher
> >
> > European Commission - DG JRC
> > Institute for Environment and Sustainability (IES). Unit H03 – FRC
> > Via Fermi, 2749
> > I-21027 Ispra (VA) - Italy - TP 261
> >
> > Tel. +39 0332 78 3600
> > margherita.di-...@jrc.ec.europa.eu
> >
> > Disclaimer: The views expressed are purely those of the writer and may
> not
> > in any circumstance be regarded as stating an official position of the
> > European Commission.
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Margherita DI LEO
Postdoctoral Researcher

European Commission - DG JRC
Institute for Environment and Sustainability (IES). Unit H03 – FRC
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] attribute table manager; SQL Builder; SQL statement is not valid.

[Margherita Di Leo]

And .. I'd have another wish (pls don't kill me)
It would be nice if the features selected from the attribute table were
highlighted (for example using a different color, i.e. yellow) in the Map
Display.

Thanks
madi

On Tue, Jan 22, 2013 at 9:39 AM, Margherita Di Leo <
dileomargher...@gmail.com> wrote:

> Hi,
>
> thank you Maris.
> Would it be possible to grey out the "verify" and "apply" buttons before
> the comparison operator has been selected? This would be more intuitive.
>
> Thanks
> madi
>
>
> On Tue, Jan 22, 2013 at 7:55 AM, Maris Nartiss wrote:
>
>> Hi,
>> before pressing "Verify", You must enter comparison operator. = or LIKE
>>
>> Maris.
>>
>> 2013/1/21 Margherita Di Leo :
>> > Hi,
>> >
>> > I'm using GRASS 6.4.3svn on Red Hat. Trying to use the SQL Builder, I
>> always
>> > obtain Syntax Error on queries which are self built by the builder...
>> > Example on NC dataset:
>> > map: census_wake2000
>> > I open the attribute table manager from the GUI
>> > I select: SQL Query: Advanced
>> > Columns: TRT2000 -> Get sample -> Value: 050100 (the first on the top)
>> ->
>> > Verify
>> > I get:
>> >
>> > SQL statement is not valid.
>> >
>> > DBMI-DBF driver error:
>> > SQL parser error: syntax error, unexpected STRING processing ''050100' '
>> > in statement:
>> > SELECT * FROM census_wake2000 WHERE TRT2000 '050100'
>> > Error in db_open_select_cursor()
>> >
>> > ?
>> >
>> > Thanks,
>> > madi
>> >
>> > --
>> > Margherita DI LEO
>> > Postdoctoral Researcher
>> >
>> > European Commission - DG JRC
>> > Institute for Environment and Sustainability (IES). Unit H03 – FRC
>> > Via Fermi, 2749
>> > I-21027 Ispra (VA) - Italy - TP 261
>> >
>> > Tel. +39 0332 78 3600
>> > margherita.di-...@jrc.ec.europa.eu
>> >
>> > Disclaimer: The views expressed are purely those of the writer and may
>> not
>> > in any circumstance be regarded as stating an official position of the
>> > European Commission.
>> >
>> > ___
>> > grass-dev mailing list
>> > grass-dev@lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
>
> --
> Margherita DI LEO
> Postdoctoral Researcher
>
> European Commission - DG JRC
> Institute for Environment and Sustainability (IES). Unit H03 – FRC
> Via Fermi, 2749
> I-21027 Ispra (VA) - Italy - TP 261
>
> Tel. +39 0332 78 3600
> margherita.di-...@jrc.ec.europa.eu
>
> Disclaimer: The views expressed are purely those of the writer and may not
> in any circumstance be regarded as stating an official position of the
> European Commission.
>



-- 
Margherita DI LEO
Postdoctoral Researcher

European Commission - DG JRC
Institute for Environment and Sustainability (IES). Unit H03 – FRC
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #1858: inconsistancy g.parser on command console and command line

[GRASS GIS]

#1858: inconsistancy g.parser on command console and command line
---+
 Reporter:  pvanbosgeo |   Owner:  grass-dev@…  
 Type:  defect |  Status:  new  
 Priority:  normal |   Milestone:  7.0.0
Component:  Shell Scripts  | Version:  svn-trunk
 Keywords: |Platform:  Linux
  Cpu:  Unspecified|  
---+
 If you have a script r.test with amongst others the following in the
 header:

 {{{
 #%flag
 #%  key: s
 #%  description: run r.report on output map?
 #% answer : 1
 #%END
 }}}

 Opening the GUI interface via the command line will show the flag S unset.
 Opening the GUI interface via the command console in the GRASS GIS layer
 manager shows the flag S as set (see attached screenshot for
 clarification)

 Running GRASS 7.0 on Ubuntu 12.10

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1858: inconsistancy g.parser on command console and command line

[GRASS GIS]

#1858: inconsistancy g.parser on command console and command line
---+
 Reporter:  pvanbosgeo |   Owner:  grass-dev@…  
 Type:  defect |  Status:  new  
 Priority:  normal |   Milestone:  7.0.0
Component:  Shell Scripts  | Version:  svn-trunk
 Keywords: |Platform:  Linux
  Cpu:  Unspecified|  
---+

Comment(by martinl):

 I would say that your wish goes against logic of flags. Parser doesn't
 care about default answer for flags. In your case invert your flag.

 {{{
 #% description: do not run r.report on output map
 }}}

 I would suggest to close this ticket as 'invalid'

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] r.forestfrag

[Paulo van Breugel]

Hi,

I was trying to run r.forestfrag.sh on GRASS 7.0. It is incompatible 
however, so I decided to update it to work with GRASS 7.0.


While working on it, I have added some further options and changes:

 * The user can now select the size of the moving window (default is
   still 3x3) -- Stefan, something you were looking for I think.
   Perhaps you can test?
 * Before the areas statistics (r.report) is run, the output map is
   trimmed to remove the edge effect of the calculations with the
   moving window
 * The user can decide to keep the output map trimmed or not
 * The user has the option to keep some of the intermediate layers (off
   by default).

I have added the new version of r.forestfrag.sh to 
https://svn.osgeo.org/grass/grass-addons/grass7/raster/r.forestfrag/ to 
make it easer for other to check / correct the script. It doesn't run on 
GRASS 6.4 unfortunately, although it should be fairly easy to make it so.


Cheers,

Paulo

p.s. while working on this, I ran into the problem that g.parser seems 
to parse the GUI window differently when running from the command line 
or from the command console in the GRASS Layer Manager (as reported 
here: http://trac.osgeo.org/grass/ticket/1858)






___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1858: inconsistancy g.parser on command console and command line

[GRASS GIS]

#1858: inconsistancy g.parser on command console and command line
+---
  Reporter:  pvanbosgeo |   Owner:  grass-dev@…  
  Type:  defect |  Status:  closed   
  Priority:  normal |   Milestone:  7.0.0
 Component:  Shell Scripts  | Version:  svn-trunk
Resolution:  invalid|Keywords:   
  Platform:  Linux  | Cpu:  Unspecified  
+---
Changes (by pvanbosgeo):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 OK, point taken, closing thicket

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] attribute table manager; SQL Builder; SQL statement is not valid.

[Martin Landa]

Ciao,

2013/1/22 Margherita Di Leo :
> And .. I'd have another wish (pls don't kill me)
> It would be nice if the features selected from the attribute table were
> highlighted (for example using a different color, i.e. yellow) in the Map
> Display.

possible, but so straightforward

* right click -> Select all
* right click -> Highlight selected features

Martin

-- 
Martin Landa  * http://geo.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] attribute table manager; SQL Builder; SQL statement is not valid.

[Martin Landa]

2013/1/22 Martin Landa :
> possible, but so straightforward

*not* so ;-)

Martin

-- 
Martin Landa  * http://geo.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] attribute table manager; SQL Builder; SQL statement is not valid.

[Margherita Di Leo]

Thanks! Yes, not so intuitive I would say. Perhaps the highlight could be
automatic when features are selected.. at least, as a user I would expect
so.. but maybe other users can have different opinions..

Thank you!

madi

On Tue, Jan 22, 2013 at 2:29 PM, Martin Landa wrote:

> 2013/1/22 Martin Landa :
> > possible, but so straightforward
>
> *not* so ;-)
>
> Martin
>
> --
> Martin Landa  * http://geo.fsv.cvut.cz/~landa
>



-- 
Margherita DI LEO
Postdoctoral Researcher

European Commission - DG JRC
Institute for Environment and Sustainability (IES). Unit H03 – FRC
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] About the "-g" switch of g.region

[Nikos Alexandris]

Hi dev-list!

Is there a reason why the output of  "g.region -cg" (in decimal degrees) is 
not the same as the output of "g.region -c" (in D:M:S)?

The -g switch is there to "print in shell script style". Does the 
switch/description imply, necessarily, decimal degrees?

e.g.:

# grass70, same for grass643
g.region -c

north-south center: 40:20:04.5N
east-west center: 19:21:14.5E

# shell script style
g.region -cg

center_easting=19.354028
center_northing=40.334583

Thank you for your time,
Nikos
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] attribute table manager; SQL Builder; SQL statement is not valid.

[Moritz Lennert]

On 22/01/13 14:35, Margherita Di Leo wrote:

Thanks! Yes, not so intuitive I would say. Perhaps the highlight could
be automatic when features are selected.. at least, as a user I would
expect so.. but maybe other users can have different opinions..


I actually like the fact that I can query the table without automatic 
highlighting, but I agree that it would be nice to be able to highlight 
the selected features with one click instead of two. Maybe a solution à 
la QGIS could be an option: in the table, instead of showing only the 
tuples that result from the query, show all tuples, but with the query 
result tuples selected. Then "right click -> Highlight selected 
features" would be enough to see them in the map.


Moritz

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS6.4.3RC2 issues

[Moritz Lennert]

On 22/01/13 02:47, Helena Mitasova wrote:

Finally, among the first questions I get about GRASS is how to add legend for 
vector data layer -
is there any?


No, the only way to get a vector legend is to use ps.map (possibly via 
the new map composer). It is not possible to get a vector legend in the 
Map Display, nor in the Layer Manager.



If not, perhaps that is something for GSoC along with numerous
other cartography related capabilities (e.g. expand the symbology)
to add to either display or cartographic composer.


+1 (time to start the GSoc 2013 Ideas collection !)

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS6.4.3RC2 issues

[Moritz Lennert]

On 22/01/13 16:48, Moritz Lennert wrote:

On 22/01/13 02:47, Helena Mitasova wrote:

Finally, among the first questions I get about GRASS is how to add
legend for vector data layer -
is there any?


No, the only way to get a vector legend is to use ps.map (possibly via
the new map composer). It is not possible to get a vector legend in the
Map Display, nor in the Layer Manager.


If not, perhaps that is something for GSoC along with numerous
other cartography related capabilities (e.g. expand the symbology)
to add to either display or cartographic composer.


+1 (time to start the GSoc 2013 Ideas collection !)


Just so things don't get lost in the mailing list:

http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] About the "-g" switch of g.region

[Glynn Clements]

Nikos Alexandris wrote:

> Is there a reason why the output of  "g.region -cg" (in decimal degrees) is 
> not the same as the output of "g.region -c" (in D:M:S)?
> 
> The -g switch is there to "print in shell script style". Does the 
> switch/description imply, necessarily, decimal degrees?

I think it implies that the output is in a format amenable to use by
shell scripts.

DNS is primarily meant for humans; programs which aren't specifically
designed for geography or cartography won't understand DMS, so it will
have to be converted, and doing that in a shell script is messy (expr
and $((...)) only support integer arithmetic).

-- 
Glynn Clements 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1858: inconsistancy g.parser on command console and command line

[GRASS GIS]

#1858: inconsistancy g.parser on command console and command line
+---
  Reporter:  pvanbosgeo |   Owner:  grass-dev@…  
  Type:  defect |  Status:  closed   
  Priority:  normal |   Milestone:  7.0.0
 Component:  Shell Scripts  | Version:  svn-trunk
Resolution:  invalid|Keywords:   
  Platform:  Linux  | Cpu:  Unspecified  
+---

Comment(by glynn):

 Replying to [comment:1 martinl]:
 > Parser doesn't care about default answer for flags.
 It's more accurate to say that the default answer for a flag should always
 be zero, as it's impossible to "unset" a flag from the command line.

 r54754 modifies g.parser so that "answer" is not a valid parameter for
 flags.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Script for converting degrees clockwise from North to GRASS convention

[Margherita Di Leo]

Hi,

I figured out that sometimes it would be useful to have a script for
converting a direction map which uses the convention degrees clockwise from
North, into the GRASS convention, which is as you well know degrees from
East counterclockwise [1]. The aim is to deal with wind direction maps for
example, which often use the above mentioned convention [2], but also some
other software.
I wrote a short tentative of such conversion tool in the form of a grass
addon for myself, enclosed. I would like to know:

1) if would be of interest for anyone here, i.e. worth to be published in
the addon repo;
2) if you have any idea how to make the several time nested r.mapcalc
expression less awful :-)

If we call WIND the direction map which uses the convention degrees
clockwise from North, and GRASS the output map, the rule that I applied is:

IF 0 <= WIND < 270 ; GRASS = 270 - WIND
IF WIND = 270;  GRASS = 360
IF 270 < WIND < 360   ;  GRASS 630 - 0
IF WIND = null ; GRASS = 0
NULL otherwise (this latter I have added to check if there is any error.

If you are willing to countercheck my assumptions I'd appreciate.

cheers,
madi


[1] http://grass.osgeo.org/grass64/manuals/r.slope.aspect.html
[2] http://www.firewords.net/definitions/Wind_direction.htm

-- 
Margherita DI LEO
Postdoctoral Researcher

European Commission - DG JRC
Institute for Environment and Sustainability (IES). Unit H03 – FRC
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.


r.convert.aspect.py
Description: Binary data
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] About the "-g" switch of g.region

[Nikos Alexandris]

Nikos Alexandris wrote:

> > Is there a reason why the output of  "g.region -cg" (in decimal degrees)
> > is not the same as the output of "g.region -c" (in D:M:S)?

> > The -g switch is there to "print in shell script style". Does the
> > switch/description imply, necessarily, decimal degrees?

Glynn Clements wrote:
 
> I think it implies that the output is in a format amenable to use by
> shell scripts.
 
> DNS is primarily meant for humans; programs which aren't specifically
> designed for geography or cartography won't understand DMS, so it will
> have to be converted, and doing that in a shell script is messy (expr
> and $((...)) only support integer arithmetic).

For the records, I require(d) a bunch of Landsat scene center coordinates. 
Yes, in decimal degrees to feed the i.atcorr module. But, it took me a while, 
to find it (-g). I was sure I have "grepped" decimal degrees from a grass-
module before -- couldn't recall, however, which one.

Personally a I would prefer a (slightly) different description for the switch, 
or, at the very least, some additional note in the manual.

Thank you Glynn, Nikos

signature.asc
Description: This is a digitally signed message part.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #1859: d.mon is broken

[GRASS GIS]

#1859: d.mon is broken
+---
 Reporter:  huhabla |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  critical|   Milestone:  7.0.0
Component:  Display | Version:  svn-trunk
 Keywords:  d.mon, wx0  |Platform:  Linux
  Cpu:  x86-64  |  
+---
 {{{
 GRASS 7.0.svn (utm43wgs84):~/src/grass7.0 > d.mon wx0
 GRASS 7.0.svn (utm43wgs84):~/src/grass7.0 > Traceback (most recent call
 last):
   File "/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-
 gnu/etc/gui/wxpython/mapdisp/main.py", line 332, in 
 gmMap = MapApp(0)
   File "/usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode/wx/_core.py",
 line 7981, in __init__
 self._BootstrapApp()
   File "/usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode/wx/_core.py",
 line 7555, in _BootstrapApp
 return _core_.PyApp__BootstrapApp(*args, **kwargs)
   File "/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-
 gnu/etc/gui/wxpython/mapdisp/main.py", line 249, in OnInit
 size = monSize)
   File "/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-
 gnu/etc/gui/wxpython/mapdisp/frame.py", line 94, in __init__
 self.AddToolbar(toolb)
   File "/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-
 gnu/etc/gui/wxpython/mapdisp/frame.py", line 377, in AddToolbar
 self.toolbars['map'] = MapToolbar(self, self.Map)
   File "/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-
 gnu/etc/gui/wxpython/mapdisp/toolbars.py", line 90, in __init__
 log.WriteCmdLog(_('3D view mode not available'))
 UnboundLocalError: local variable 'log' referenced before assignment
 }}}

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1859: d.mon is broken

[GRASS GIS]

#1859: d.mon is broken
+---
 Reporter:  huhabla |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  critical|   Milestone:  7.0.0
Component:  Display | Version:  svn-trunk
 Keywords:  d.mon, wx0  |Platform:  Linux
  Cpu:  x86-64  |  
+---

Comment(by wenzeslaus):

 It is working for me on Ubuntu 10.04 and 12.04, grass 7 r54755.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1859: d.mon is broken

[GRASS GIS]

#1859: d.mon is broken
+---
 Reporter:  huhabla |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  critical|   Milestone:  7.0.0
Component:  Display | Version:  svn-trunk
 Keywords:  d.mon, wx0  |Platform:  Linux
  Cpu:  x86-64  |  
+---

Comment(by huhabla):

 Besides the fact that it is not working for me on two different Ubuntu
 12.04 machines, is this part of code bad style:
 gui/wxpython/mapdisp/toolbars.py line 82 - 91
 {{{
 if self.parent.GetLayerManager():
 log = self.parent.GetLayerManager().GetLogWindow()

 if haveNviz:
 choices.append(_('3D view'))
 self.toolId['3d'] = 1
 else:
 from nviz.main import errorMsg
 log.WriteCmdLog(_('3D view mode not available'))
 log.WriteWarning(_('Reason: %s') % str(errorMsg))
 }}}

 What happens in case there is no parent with a layer manager? In this case
 the application crashes! This exception should be handled, for example to
 use a
 different log window or the console log?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1859: d.mon is broken

[GRASS GIS]

#1859: d.mon is broken
+---
 Reporter:  huhabla |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  critical|   Milestone:  7.0.0
Component:  Display | Version:  svn-trunk
 Keywords:  d.mon, wx0  |Platform:  Linux
  Cpu:  x86-64  |  
+---

Comment(by wenzeslaus):

 Replying to [comment:2 huhabla]:
 > Besides the fact that it is not working for me on two different Ubuntu
 12.04 machines

 I don't understand what is your configuration. The error means that you
 don't have NVIZ.

 > is this part of code bad style:
 > gui/wxpython/mapdisp/toolbars.py line 82 - 91
 >
 > What happens in case there is no parent with a layer manager? In this
 case the application crashes! This exception should be handled, for
 example to use a
 > different log window or the console log?

 You are completely right! This is subject to ongoing refactoring
 (currently paused). This will be fixed, probably, in next days. (Anna will
 provide fix for now.)

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev