On Tue, Feb 15, 2011 at 5:29 AM, Jan Kovanda <kovandajan11191@xxxxxxxxx> wrote: > At first I thought that using gegl_exit() should delete (unref and free) > module_db. A bit of testing revealed some unpleasant surprises. Even after > gegl_exit() I am still able to access GeglNodes a gegl methods as if no exit was > called. > > Then what is method gegl_exit() good for? GEGL is not designed to be torn down and reinitialized, gegl_exit will cause unreferencing some of the runtime data as well as report any problems detected by sanity checks. Patches making it possible to reload the GEGL ops would be welcome, do however note that the GType system underlying GObject is likely to provide some unexpected hurdles. /Øyvind K. -- «The future is already here. It's just not very evenly distributed» -- William Gibson http://pippin.gimp.org/ ; http://ffii.org/ _______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
