[GRASS-dev] Suggestion: wxGUI as default in G6.4

[Helena Mitasova]

It seems that vector display is still causing problems when GRASS is installed under C:\Program Files
see below:

Helena

computers and systems:
personal laptop:
> cpu:AMD Turion x2 ultra dual core mobile zm-82 2.2Ghz
> windows 7 professional 64 bit

> office dekstop:
> cpu:Intel Core 2 Quad Q6600 2.4Ghz
> Windows 7 professional 64 bit)


I tested the latest - they still crash when installed in the default installation folder (C:\Program Files (x86)\GRASS-64-SVN) - both work good when I install them in a folder that does not contain any spaces in the path name (C:\GRASS64). So no change since I last tested both versions.

previous message
I was able to display vectors 1 - 2 times then it starts crashing (in both 64 and 65 - It used to crash every time I used d.vect)
when I say d.vect - it is not command line, I am using the GUI.
the error message from windows syas that python.exe crashes.
in the msys it says: "bad file descriptor"


Helena Mitasova
Associate Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
Raleigh, NC 27695
hmitaso at unity.ncsu.edu



On Feb 26, 2010, at 10:04 AM, Markus Neteler wrote:

> On Fri, Feb 12, 2010 at 7:22 AM, Glynn Clements
> <glynn at gclements.plus.com> wrote:
>> 
>> Markus Neteler wrote:
>> 
>>> ... as the subject indicate: any objections to change to wxGUI as default?
> 
> I am still MUCH in favour of this change.
> 
>>> Make this change from 6.4.0 to 6.4.1 isn't much policy compliant.
>>> And I would like to avoid to publish a 6.5 rather than focusing on 7...
>> 
>> My main concern is that there should be some way to prevent the GUI
>> from loading the vdigit and nviz modules.
> 
> I agree. Is that hard to accomplish?
> 
> My brute-force method is (in GRASS):
> 
> rm -rf $GISBASE/etc/wxpython/nviz $GISBASE/etc/wxpython/vdigit
> 
> then 'g.gui wxpython' works.
> 
>> AFAIK, it handles the case where these modules don't exist. But if
>> they do exist and there's something wrong with them (binary
>> compatibility issues), the whole GUI is toast.
> 
> ... which is unacceptable and currently the case on my laptop.
> So a functionality test (or whatever) before loading  the vdigit and
> nviz modules would be needed. Since the tcl versions of both are
> accessible, I don't see it as showstopper to have the wxGUI as
> default GUI *if the test was added* and wxnviz and wxvdigit fail.
> 
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev