Opened 17 years ago
Closed 16 years ago
#103 closed defect (worksforme)
wx-python gui: NVIZ (tcltk) not starting
Reported by: | hellik | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.0 |
Component: | wxGUI | Version: | svn-trunk |
Keywords: | wx-python-gui, NVIZ | Cc: | |
CPU: | Unspecified | Platform: | MSWindows XP |
Description
hi,
i've compiled a today's svn-trunk-checkout. the NVIZ-start-dialogue starts normally, but if i want to run NVIZ with:
command with spearfish on the wxpython-gui nviz elevation=elevation.dem@PERMANENT color=elevation.dem@PERMANENT
following error message (english translation of a german error message) comes up: "error in command execution n: [Error2] system could not find the file"
NVIZ out of the tcltk-gui works fine
helli
-- svn-checkout trunk: 2008/03/19 afternoon -- system: win xp (german) python 2.5.1 wxpython 2.8.7.1 tcl/tk 8.5.1 --
Change History (8)
comment:1 by , 17 years ago
Keywords: | MS Windows added |
---|
comment:2 by , 17 years ago
Milestone: | 6.3.0 → 6.4.0 |
---|
comment:3 by , 17 years ago
Component: | Python → wxGUI |
---|
comment:4 by , 16 years ago
CPU: | → Unspecified |
---|---|
Keywords: | MS Windows removed |
Platform: | → MSWindows XP |
comment:5 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:6 by , 16 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
windows vista
osgeo4w (2008/02/08):
grass64rc3-2 GDAL 1.5.4, released 2009/01/07
data:
gisdemo_ncspm
the wxgui-menue "NVIZ (requires Tcl/Tk)" from the drop-down-menue for input starts normally:
nviz elevation=elevation@PERMANENT color=elevation@PERMANENT
no error-message, but nothing happens.
NVIZ out of the tcltk-gui works fine
comment:7 by , 16 years ago
Priority: | major → normal |
---|
comment:8 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
I just tried this on the Mac OSX with GRASS 6.4 and 6.5, compiled 18 April 2009. NVIZ launches fine from the wxPython GUI, from the wxPython command terminal, and from the regular unix terminal.
I wonder if this is a result of the Windows build not adding *.exe to the nviz binary startup file? The Windows binary has been considerably improved since 19 March (date of the checkout listed above). So maybe this is fixed.
Michael
There have been some changes to nviz since July. At least on the Mac, this works OK now. Please test on other platforms and report back. Thanks.