Hi, If I interpret the term "cookie cutter" correctly you are referring to the intersect tool? I'm not sure simply editing the original layer without decent backup is a good idea. The better solution is to have in-memory layers which don't force you to always specify a target path but can be saved if needed. This is already covered by Sextante.
Best wishes, Anita On Tue, Feb 12, 2013 at 9:12 PM, Régis Haubourg <regis.haubo...@eau-adour-garonne.fr> wrote: > Hi, > +1, and I remember Anita Graser voting for that too. > IMHO, this is more a core feature to fund or develop than a plugin . > Please consider contributing to help us, there are so many features being > worked at the moment (new API 2.0, Sextante... doc... android...). You can > help in many ways (file a ticket, write detailed specs..) I have some > funding capabilities, but I am struggling to find some time to write > contracts.. > Régis > > > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/Cookie-cutter-tp5033786p5033795.html > Sent from the Quantum GIS - User mailing list archive at Nabble.com. > _______________________________________________ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-user _______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user