Hello, I still think that setting inmature GUI as default one isn't the best idea. On my ~amd64 box I'm unable to start wxgui with g.gui (no error), launch from init.sh almost works (just tested - recent svn up has fixed some actions with NULL/NotAnObject). New wxgui will be really good UI, still right now I still preffer old gis.m.
Sorry for rant, Maris. 2009/9/22, Hamish <[email protected]>: > Hi, > > Is it possible to have g.gui detach the GUI from the terminal prompt? > That is typically what you'd want to happen. ^Z + bg are redundant > keystrokes / cumulatively lost moments. The man pages shouldn't have > to suggest to do "g.gui $GUI &". g.gui isn't the program, it's just > the launcher. > > I am trying 6.5 with default wx on Debian/Etch which has no wx2.8 in it. > > "g.gui" fails cleanly enough with an error message that there is no wx, > but it feels sort of like a "what now?" situation. ("g.gui --ui" isn't > exactly an obvious solution, maybe put that in the init.sh startup help) > > at least the module GUIs are still tcl/tk so you can use them. > > if we set the default wx now we are in practice making wxwidgets a > mandatory dependency for that release. (not technically, but it can > seem that way) > > Probably wx2.8 has made it into most systems these days; I'm just > wondering how best to facilitate the fail-safe mode. > > > > Hamish > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
