Hi,
2008/9/8 Glynn Clements [EMAIL PROTECTED]:
I don't know about the easiest way, but the only robust solution is to
keep nagging the wxGUI developers until they move the high-risk
features (vdigit, nviz) out of the main wxGUI process.
it's my plan, I started to elaborate with NvizThread
Martin Landa wrote:
I don't know about the easiest way, but the only robust solution is to
keep nagging the wxGUI developers until they move the high-risk
features (vdigit, nviz) out of the main wxGUI process.
it's my plan, I started to elaborate with NvizThread in
Hi,
2008/9/8 Glynn Clements [EMAIL PROTECTED]:
I don't know about the easiest way, but the only robust solution is to
keep nagging the wxGUI developers until they move the high-risk
features (vdigit, nviz) out of the main wxGUI process.
it's my plan, I started to elaborate with NvizThread in
Michael Barton wrote:
3) i.attcorr no longer compiles. Here is the error.
main.cpp:309: error: �isnan� was not declared in this scope
make: *** [OBJ.i386-apple-darwin9.4.0/main.o] Error 1
isnan() isn't part of the C++ standard. It may be provided as an
extension by some versions of gcc, or
Martin Landa wrote:
I don't know about the easiest way, but the only robust solution is to
keep nagging the wxGUI developers until they move the high-risk
features (vdigit, nviz) out of the main wxGUI process.
it's my plan, I started to elaborate with NvizThread in nviz_mapdisp.py...
I just updated from develbranch_6 after a couple of weeks. Here are
some remaining problems in compiling and a showstopper with running
GRASS.
1) vdigit: compiles fine now. BUT it probably keeps the wxPython GUI
from running now (see below).
2) wxnviz: still doesn't compile but gets a
