Hi,
1) What do I have completed this week?
I changed the layout of view page. I added cutting planes functionality, I'm considering
changing the XY control, but I'm not sure how it should look like yet.
2) What am I going to achieve for next week?
Because of my approaching bachelor final exams, I won't be
able to work much on wxNviz. However I intend to concentrate fully on
wxNviz after that.
3) Is there any blocking issue?
Nothing except for the exams.
Anna
On 10/06/11 14:02, Anna Kratochvílová wrote:
Hi,
1) What do I have completed this week?
I changed the layout of view page. I added cutting planes functionality, I'm considering
changing the XY control, but I'm not sure how it should look like yet.
Thank you for the great work. I just updated my source and reompiled and trying to launch 3d view immediately crashes the entire GUI, without any error message on the console. I tried with export WX_DEBUG=5, but still not message. Any hints how I could debug this to get some idea why this is happening ?
Moritz
Moritz,
I just tested it and you are probably trying to start it with vector data generated in grass64,
if you want to use vector data in grass7 you need to rebuild the topology.
I just tried the latest updates - it works fine for me and it has a lot of cool updates.
It crashed when I tried to add vector layer in grass64 format.
I am wondering whether it would be possible to handle the different vector format in grass7 without crashing -
not just for wxnviz but other modules as well
For testing purposes I have created a new mapset with copies of vector data with rebuilt topology for grass7
but there needs to be a better way.
Helena
On Jun 10, 2011, at 8:48 AM, Moritz Lennert wrote:
On 10/06/11 14:02, Anna Kratochvílová wrote:
Hi,
1) What do I have completed this week?
I changed the layout of view page. I added cutting planes functionality, I'm considering
changing the XY control, but I'm not sure how it should look like yet.Thank you for the great work. I just updated my source and reompiled and trying to launch 3d view immediately crashes the entire GUI, without any error message on the console. I tried with export WX_DEBUG=5, but still not message. Any hints how I could debug this to get some idea why this is happening ?
Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On 10/06/11 15:46, Helena Mitasova wrote:
Moritz,
I just tested it and you are probably trying to start it with vector data generated in grass64,
if you want to use vector data in grass7 you need to rebuild the topology.
I just tried the latest updates - it works fine for me and it has a lot of cool updates.
It crashed when I tried to add vector layer in grass64 format.
I don't think that this is the problem here: I've tried creating a new vector file, not digitizing an old one.
And for wxnviz, it crashes when I only have the nc_spm elevation layer loaded, nothing else, so no vectors involved.
In grass6dev digitization works, but I also get a crash in wxnviz...
As I said, I'm mostly looking for a way to find more debug information.
Moritz
Hi,
2011/6/10 Moritz Lennert <mlennert@club.worldonline.be>:
Thank you for the great work. I just updated my source and reompiled and
trying to launch 3d view immediately crashes the entire GUI, without any
error message on the console. I tried with export WX_DEBUG=5, but still not
this variable is not environmental, so you need to use `g.gisenv`
(like for DEBUG).
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Hi,
2011/6/10 Helena Mitasova <hmitaso@ncsu.edu>:
I just tested it and you are probably trying to start it with vector data generated in grass64,
if you want to use vector data in grass7 you need to rebuild the topology.
I just tried the latest updates - it works fine for me and it has a lot of cool updates.
It crashed when I tried to add vector layer in grass64 format.
it should not crash, try digitizer, you should get a dialog for
rebuilding topology when opening vector for editing.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Hi,
2011/6/10 Anna Kratochvílová <KratochAnna@seznam.cz>:
1) What do I have completed this week?
I changed the layout of view page. I added cutting planes functionality, I'm considering
changing the XY control, but I'm not sure how it should look like yet.
good, see also Anna's screenshots on the wiki
http://grass.osgeo.org/wiki/WxNviz_GSoC_2011#Week_2_.28June_6.29
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
On 10/06/11 17:56, Martin Landa wrote:
Hi,
2011/6/10 Moritz Lennert<mlennert@club.worldonline.be>:
Thank you for the great work. I just updated my source and reompiled and
trying to launch 3d view immediately crashes the entire GUI, without any
error message on the console. I tried with export WX_DEBUG=5, but still notthis variable is not environmental, so you need to use `g.gisenv`
(like for DEBUG).
Duh, I knew that...too many things going on at once. Sorry.
Here's what I get when adding the elevation layer to the display and then launching wxnviz (grass7, on Debian Squeeze GNU/Linux, 32bit and --enable-largefile - currently recompiling without, python 2.6.6, wx 2.8.10.1):
GUI D3/5: Map.Render() type=raster, layer=elevation@PERMANENT
GUI D1/5: gcmd.RunCommand(): g.pnmcomp opacity=1.0 mask=/tmp/tmpi54BNS.pgm height=531 width=798 background=255:255:255:255 input=/tmp/tmpi54BNS.ppm output=/tmp/tmp590e19.ppm
GUI D2/5: gcmd.RunCommand(): command started
GUI D3/5: gcmd.RunCommand(): decoding string
GUI D1/5: gcmd.RunCommand(): get return code 0
GUI D3/5: gcmd.RunCommand(): print error
GUI D3/5: gcmd.RunCommand(): print read error
GUI D3/5: Map.Render() force=True file=/tmp/tmp590e19.ppm
GUI D5/5: BufferedWindow.Draw(): id=99, pdctype = image, coord=[0, 0, 0, 0]
GUI D3/5: Map.GetListOfLayers(): numberof=0
GUI D1/5: BufferedWindow.UpdateMap(): render=True, renderVector=True -> time=0.02
GUI D4/5: BufferedWindow.OnPaint(): redrawAll=True
GUI D3/5: CreateTool(): tool=628, label=view bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb3e0028> >
GUI D3/5: CreateTool(): tool=629, label=surface bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb3e7950> >
GUI D3/5: CreateTool(): tool=630, label=vector bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb3fdff0> >
GUI D3/5: CreateTool(): tool=631, label=volume bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb39e7c0> >
GUI D3/5: CreateTool(): tool=632, label=light bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb39e7a0> >
GUI D3/5: CreateTool(): tool=633, label=fringe bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb27dac8> >
GUI D3/5: CreateTool(): tool=634, label=settings bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xabceb98> >
GUI D3/5: CreateTool(): tool=635, label=help bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xb3f9978> >
GUI D3/5: CreateTool(): tool=636, label=quit bitmap=<wx._gdi.Bitmap; proxy of <Swig Object of type 'wxBitmap *' at 0xabcf1b8> >
GUI D5/5: BufferedWindow.Draw(): id=None, pdctype = clear, coord=[0, 0, 0, 0]
GUI D5/5: BufferedWindow.Draw(): id=None, pdctype = clear, coord=[0, 0, 0, 0]
GUI D5/5: BufferedWindow.Draw(): id=None, pdctype = clear, coord=[0, 0, 0, 0]
GUI D4/5: BufferedWindow.OnPaint(): redrawAll=True
GUI D3/5: Map.AdjustRegion(): {u'rows': 531.0, u'e': 645000.0, u'cells': 423738.0, u'cols': 798.0, u'center_northing': 221750.0, u'n': 228500.0, u'center_easting': 637500.0, u's': 215000.0, u'w': 630000.0, u'ewres': 18.796992481203006, u'nsres': 25.423728813559322}
GUI D3/5: Map.SetRegion(): n-s resol: 25.423729; n-s resol3: 10; rows: 531; north: 228500.0; t-b resol: 1; zone: 0; bottom: 0; rows3: 1350; west: 630000.0; top: 1; cols: 798; cols3: 1500; depths: 1; e-w resol: 18.796992; proj: 99; e-w resol3: 10; east: 645000.0; south: 215000.0;
This is where it crashes, with no more messages.
I'm a bit intrigued by the mentions of "Swig Object". Do we still use swig or is this just a name coincidence ?
Moritz
Hi,
2011/6/10 Moritz Lennert <mlennert@club.worldonline.be>:
I'm a bit intrigued by the mentions of "Swig Object". Do we still use swig
or is this just a name coincidence ?
wxPython uses Swig. So it's not related to GRASS.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Hi,
this problem is caused by the today's commit?
I can add some debug messages, but I'm not sure it helps.
Anna