From: Meek, A. <All...@dr...> - 2007-02-15 21:12:30
|
Hi, Are there any specific reasons why a call to GvPoiTool's function set_point would cause a crash? I've traced a bug in my application down to a line that calls set_point. In Windows, I get a "python.exe has encountered a problem and needs to close." window. In Linux, I get segmentation fault/core dumped. I figured I'd ask this question without any specifics in case there is an easy answer. Thanks, Allan Meek |
From: William H. <wh...@nb...> - 2007-02-15 21:24:55
|
I have had a similar problem. I traced the problem as far as the file gvpoitool.c In the fuction gv_poi_tool_new_point a call is made to gv_view_area_queue_draw with argument GV_TOOL(tool)->view. Unfortunately this is null. An attempt to dereference this caused a seq fault. You can surpress the seq fault with a simple if but the bigger problem is, "why is there no associated view". I have not gone into tool initialization. - William Hughes Meek, Allan wrote: >Hi, > >Are there any specific reasons why a call to GvPoiTool's function >set_point would cause a crash? I've traced a bug in my application down >to a line that calls set_point. > >In Windows, I get a "python.exe has encountered a problem and needs to >close." window. In Linux, I get segmentation fault/core dumped. I >figured I'd ask this question without any specifics in case there is an >easy answer. > >Thanks, >Allan Meek > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys-and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Openev-discuss mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/openev-discuss > > > |
From: Mario B. <st...@gm...> - 2007-02-16 03:42:33
|
Hi, On 2/15/07, William Hughes <wh...@nb...> wrote: > > In the fuction gv_poi_tool_new_point > a call is made to gv_view_area_queue_draw > with argument GV_TOOL(tool)->view. > Unfortunately this is null. I have had probs understanding the Tools stuff myself in OpenEV2 as well (it basically works the same way). I found it to be confusing. Seems you have to make calls to gview.Toolbox.activate(viewarea) sometimes but I'm not sure why or in what circumstances. cheers -- Mario B. |
From: William H. <wh...@nb...> - 2007-02-16 13:20:01
|
Mario Beauchamp wrote: > Hi, > > On 2/15/07, William Hughes <wh...@nb...> wrote: > >> >> In the fuction gv_poi_tool_new_point >> a call is made to gv_view_area_queue_draw >> with argument GV_TOOL(tool)->view. >> Unfortunately this is null. > > > I have had probs understanding the Tools stuff myself in OpenEV2 as > well (it basically works the same way). I found it to be confusing. > Seems you have to make calls to gview.Toolbox.activate(viewarea) > sometimes but I'm not sure why or in what circumstances. > > cheers Thanks. (This is all OpenEV1 stuff) Calling .activate(viewarea) on the tool, not the toolbox worked. Note that there is no .activate() definied for a toolbox, only the one it inherits from GvTool. On the other hand there is a gv_toolbox_activate() definied in gvtool.c, just no binding. Calling .activate() on a toolbox will probably activate only one tool (whichever sits on top). There is a .activate_tool() defined for a toolbox. It looks like there is a missing python binding. I have not gone into the C code to see what is actually happening when .activate() is called - William |