Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#533 closed defect (wontfix)

Unusable shell for wingrass through osgeo4w

Reported by: cnielsen Owned by: grass-dev@…
Priority: minor Milestone: 6.4.0
Component: Installation Version: unspecified
Keywords: Cc:
CPU: x86-32 Platform: MSWindows XP

Description

After installing grass using osgeo4w, and then using the desktop icon to start grass, grass starts but the console is not available to type in. It's just blank and typing or hitting enter does nothing. (osgeo4w trac?)

Change History (3)

comment:1 Changed 11 years ago by cnielsen

CPU: Unspecifiedx86-32
Platform: UnspecifiedMSWindows XP

comment:2 Changed 10 years ago by cnielsen

Resolution: wontfix
Status: newclosed

Apparently the console was not meant to be used and is only there for error messages. The cmd box at the bottom of the main window, or starting grass through msys are work-arounds.

comment:3 in reply to:  2 Changed 10 years ago by hamish

Replying to cnielsen:

Apparently the console was not meant to be used and is only there for error messages. The cmd box at the bottom of the main window, or starting grass through msys are work-arounds.

No, I think that's a misreading of it. The console is there for more that just error messages and is meant to be used if present. I guess it is up to the packager to decide if to include it or not. During the debugging era of WinGrass I'd suggest to include it, but that's just my 1c.

I believe jef posted a patch to fix this for tcl/tk over on the osgeo4w trac site (# 83), just applied in 6.5svn.

https://trac.osgeo.org/osgeo4w/wiki/pkg-grass#OpenTickets

Hamish

Note: See TracTickets for help on using tickets.