Hi, just for your information, spots use masks, and, basically, just store masks ids in the iop params. For that it use a static array of 64 items. It could be increased, thought, as 64*sizeof(int) is not really big. but imho, there's no real need for that, 64 is more than sufficient for most use, and you can add a new instance if you want more.
Aldric Le 21/11/2014 14:32, Marcello Perathoner a écrit : > I'm developing a liquify tool, see previous post. > > This tool needs to draw lines and curves on the gui, and to store the > coordinates I need a variable length parameter block. But darktable only > implements fixed size parameter block. > > I temporarily `fixed´ this by allocating a huge parameter block and > hoping it will never overflow. Not an industrial-strength solution. > > The masks module solves the same problem by putting their data in a > separate table in the database. > > Q: Is it acceptable for an iop to have its own table in the database? > > Q: Will there be support for variable parameter block size in darktable? > > > ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
