On Fri, 18 May 2007, Michael Barton wrote:
You can do *almost* anything from the GUI that you can do from the command
line. Apparently, nviz is the biggest problem--but I don't know why it
shouldn't run.
Nviz was working great on Windows until early December (even with
Michael's new improvments and tidying of the GUI) when Bob changed it
back to use a shell script-based startup instead of starting the binary directly. Obviously that doesn't work on Windows and that meant it no longer got regularly tested on Windows. Now, if I switch it back to generate the binary directly (see attachment) it still doesn't work - gets stuck on the Please Wait stage again - so I guess some other incompatible thing was changed in the meantime. I suppose worth trying with different Tcl/Tk versions though.
I don't like committing patches that seem like the best way to solve a problem but are only part of the solution (i.e. its still broken after the patch but the patch was my best effort sort of thing), as it may hinder somebody else's efforts to fix things in the future, so have attached to this e-mail.
Paul
(attachments)
diff.txt (3.32 KB)
Paul,
The change to a script startup for nviz was at the request of other
developers.
Note that there are other ways to start nviz. If you have a command line
you can directly call the the binary (interpreter) with something
like ...
$GISBASE/etc/nviz2.2/nviz -f $GISBASE/etc/nviz2.2/scripts/nviz2.2_script
-q
which is similar to calling "wish -f somefile.tcl"
Another way, which may be a better solution for windows is to edit the
nviz2.2_script file and replace "#!/nviz -f" with "#!
$GISBASE/etc/nviz2.2/nviz -f". You may need to enter the full path for
$GISBASE. After editing the file copy it to $GISBASE/bin/nviz
(overwriting the old nviz script). Make sure it is executable. Run nviz
(formerly nviz2.2_script).
Hope this helps.
--
Bob
On Sat, 2007-05-19 at 10:06 +0100, Paul Kelly wrote:
On Fri, 18 May 2007, Michael Barton wrote:
> You can do *almost* anything from the GUI that you can do from the command
> line. Apparently, nviz is the biggest problem--but I don't know why it
> shouldn't run.
Nviz was working great on Windows until early December (even with
Michael's new improvments and tidying of the GUI) when Bob changed it
back to use a shell script-based startup instead of starting the binary
directly. Obviously that doesn't work on Windows and that meant it no
longer got regularly tested on Windows. Now, if I switch it back to
generate the binary directly (see attachment) it still doesn't work - gets
stuck on the Please Wait stage again - so I guess some other incompatible
thing was changed in the meantime. I suppose worth trying with different
Tcl/Tk versions though.
I don't like committing patches that seem like the best way to solve a
problem but are only part of the solution (i.e. its still broken after
the patch but the patch was my best effort sort of thing), as it may
hinder somebody else's efforts to fix things in the future, so have
attached to this e-mail.
Paul
_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev