Opened 15 years ago

Closed 14 years ago

#1616 closed bug (fixed)

v.kernel and r.surf.fractal overwriting and not showing results

Reported by: pcav Owned by: nobody
Priority: minor: annoyance Milestone: Version 1.0.3
Component: GRASS Version: Trunk
Keywords: Cc: grass-dev@…
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

Several modules (I found v.kernel and r.surf.fractal) don't check if a layer exist before overwriting it. When the analysis is finished, the same modules do not show the "Show output" button, so to load a raster one has to go back to data browser.

Change History (7)

comment:1 by rugginoso, 15 years ago

Please report in the grass bugtracker.

comment:2 by pcav, 15 years ago

Cc: grass-dev@… added
Platform: DebianAll

It appears to be a GRASS, not a QGIS, bug

in reply to:  description comment:3 by hamish, 15 years ago

Replying to pcav:

Several modules (I found v.kernel and r.surf.fractal) don't check if a layer exist before overwriting it.

r.surf.fractal apparently fixed in svn some months ago, v.kernel currently not.

see https://trac.osgeo.org/grass/ticket/635

When the analysis is finished, the same modules do not show the "Show output" button, so to load a raster one has to go back to data browser.

no idea about that part of it.

Hamish

comment:4 by pcav, 15 years ago

Thanks Hamish. So I assume r.surf.fractal is fixed in grass64rc>=4, right? Would it be possible to fix in the same way also v.kernel, perhaps before grass64 final?

in reply to:  4 comment:5 by hamish, 15 years ago

Replying to pcav:

Thanks Hamish. So I assume r.surf.fractal is fixed in grass64rc>=4, right?

It should be fixed since 6.4.0RC1 (Xmas 2008). Does it still fail with the latest QGIS build?

Would it be possible to fix in the same way also v.kernel, perhaps before grass64 final?

v.kernel is a bit more tricky because of the funky way it reuses the same option for both raster and vector output map names. I don't think it is too hard to manually code around that (probably can reuse some code from other modules) but someone else will have to do it -- I'm stretched rather thin with my "real-life" job right now, and that has to take precedence.

regards, Hamish

comment:6 by lutra, 14 years ago

Hi, has v.kernel been fixed since the last comment?

cheers

comment:7 by rblazek, 14 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.