Apparently, seamonkey is hard-wired into the nviz help function. I suggest
that you either allow the use of any web browser (including lynx and links)
or provide a configuration variable where we can specify which browser to
use.
Rich
___
grass-user m
Rich Shepard wrote:
> Apparently, seamonkey is
> hard-wired into the nviz help function. I suggest
> that you either allow the use of any web browser (including
> lynx and links)
> or provide a configuration variable where we can specify
> which browser to use.
GRASS> g.manual variables
look f
Helo,
I've used NVIZ in the past and not had this problem but after rebuilding
Grass/Nviz for a new system (Slackware 13 64bit) I now find when I try to
"fly" to move the landscape it keeps resetting back to its originall
position after a few frames.ie: it will start to move in the direction
Known issue, currently no fix.
http://trac.osgeo.org/grass/ticket/46
Maris.
2010/6/14, Kwas :
>
> Helo,
> I've used NVIZ in the past and not had this problem but after rebuilding
> Grass/Nviz for a new system (Slackware 13 64bit) I now find when I try to
> "fly" to move the landscape it keeps
Hi Maris,
Thanks for the reply! Too bad. I guess I'll have to install on a 32bit
system. For what it's worth my system is Slackware 13.0 64bit and also
Nvidia driver, so nothing really new to add to the bug report other
than the variance in linux distribution.
Any speculation where this bug
Hello,
at first - You can compile 32bit version on 64bit machine (if it's
possible on Slackware).
Second - once I took a look at code. It was not good, still I didn't
managed to find the root cause.
Fly mode is TCL/C hybrid.
TCL part is here:
http://trac.osgeo.org/grass/browser/grass/branches/deve
Yes, I my slackware can run
32bit apps. I tried recompiling grass without the --enable-64bit option
but still had the same nviz problem , although i expect i'm still
compiling to 64bit.
However, I've looked at the togl_flythrough.c code and found the
problem. Or at least found a change the
