[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qgis-developer
Subject:    [Qgis-developer] extremely verbose debug info editing GRASS vectors
From:       Maciej Sieczka <tutey () o2 ! pl>
Date:       2008-08-28 12:39:01
Message-ID: 48B69C65.2020304 () o2 ! pl
[Download RAW message or body]

Opening a huge GRASS vector map in GRASS Edit makes QGIS print tones of
debug info (if built with debug) which ruins performance:

> Debug: /home/shoofi/src/straight/qgis-trunk/src/plugins/grass/qgsgrassedit.cpp: \
>                 1814: (displayIcon) entered.
> Debug: /home/shoofi/src/straight/qgis-trunk/src/plugins/grass/qgsgrassedit.cpp: \
>                 1789: (displayNode) node = 13685
> Debug: /home/shoofi/src/straight/qgis-trunk/src/plugins/grass/qgsgrassedit.cpp: \
>                 1814: (displayIcon) entered.
> Debug: /home/shoofi/src/straight/qgis-trunk/src/plugins/grass/qgsgrassedit.cpp: \
>                 1789: (displayNode) node = 13686
> Debug: /home/shoofi/src/straight/qgis-trunk/src/plugins/grass/qgsgrassedit.cpp: \
>                 1814: (displayIcon) entered.
> Debug: /home/shoofi/src/straight/qgis-trunk/src/plugins/grass/qgsgrassedit.cpp: \
> 1789: (displayNode) node = 13687

... and so forth.

Could it be fixed so that QGIS built with debug can be still used for
editing GRASS vectors?

Cheers,
Maciek

-- 
Maciej Sieczka
www.sieczka.org
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


[prev in list] [next in list] [prev in thread] [next in thread]