I think I've fixed the bug that was preventing the GUI from launching in GRASS7. It looks like it was incorrect shell syntax at line 599 in function.sh. I've just committed this to the trunk svn in r41134.
Could someone please test in other platforms. Does this need to be backported to 6.5?
Michael
Michael wrote:
I think I've fixed the bug that was
preventing the GUI from launching in GRASS7. It looks like
it was incorrect shell syntax at line 599 in function.sh.
I've just committed this to the trunk svn in r41134.Could someone please test in other platforms. Does this
need to be backported to 6.5?
for me on linux the wx GUI starts fine in grass7 without the change,
both from the GUI location/mapset picker and with the mapset dir
specified on the command line.
As wxgui.py has no '#!/usr/bin/env python' shebang at the start of it
I'm sort of surprised it does work actually.
Hamish
Michael wrote:
Does this need to be backported to 6.5?
No. There wxgui.py is started by the "gui/wxpython/wxgui" shell script.
Hamish
On Feb 20, 2010, at 6:11 PM, Hamish wrote:
Michael wrote:
I think I've fixed the bug that was
preventing the GUI from launching in GRASS7. It looks like
it was incorrect shell syntax at line 599 in function.sh.
I've just committed this to the trunk svn in r41134.Could someone please test in other platforms. Does this
need to be backported to 6.5?for me on linux the wx GUI starts fine in grass7 without the change,
both from the GUI location/mapset picker and with the mapset dir
specified on the command line.As wxgui.py has no '#!/usr/bin/env python' shebang at the start of it
I'm sort of surprised it does work actually.Hamish
Yeah. I think that this "broke" when Glynn fixed incorrect syntax in a couple of places in init.sh and function.sh. So it seems like the gui was launching for the wrong reasons. When fixed, it didn't launch.
Michael