Opened 11 years ago

Closed 7 years ago

#196 closed defect (fixed)

wxGUI interface hangs, when adding maps to display

Reported by: rmatev Owned by: grass-dev@…
Priority: minor Milestone: 6.4.0
Component: wxGUI Version: 6.3.0
Keywords: Cc:
CPU: x86-32 Platform: MSWindows XP

Description

When I set DEBUG=4 or DEBUG=5 and then add a vector map to map display 1 (which was empty), the whole wxpython interface hangs (before the map is added). The same thing happens, if DEBUG is set to 0, 1, 2, or 3, then a map is loaded into map display 1, then DEBUG is changed to 4, and the display is refreshed.

Change History (8)

comment:1 Changed 11 years ago by rmatev

Version: unspecified6.3.0

comment:2 Changed 11 years ago by cmbarton

Resolution: fixed
Status: newclosed

This is fixed in GRASS 6.4

comment:3 Changed 11 years ago by martinl

Resolution: fixed
Status: closedreopened

This issue is still open... It hasn't been fixed AFAIK.

comment:4 Changed 10 years ago by cmbarton

I've just tested this on 6.4 and 6.5 svn with Mac OSX. I have no problems. No hanging with DEBUG=4 set. Is this still a problem for anyone else?

Michael

comment:5 in reply to:  4 Changed 10 years ago by martinl

Replying to cmbarton:

I've just tested this on 6.4 and 6.5 svn with Mac OSX. I have no problems. No hanging with DEBUG=4 set. Is this still a problem for anyone else?

yes,

g.gisenv set=DEBUG=5
  • start wxGUI
  • add new vector map layer
  • display

wxGUI stops responding because of amount of debug messages redirected to command output window.

comment:6 Changed 10 years ago by cmbarton

Is this something we want to fix or are even able to fix? This is not a normal use scenario. How *could* it be fixed? Send output to a log?

Michael

comment:7 Changed 9 years ago by neteler

Is this still an issue?

comment:8 Changed 7 years ago by neteler

Resolution: fixed
Status: reopenedclosed

No answer, closing.

Note: See TracTickets for help on using tickets.