P Le 21/01/2013 22:12, Pascal Obry a écrit : > Aldric, > >> parafin propose a solution : duplicating struct and iop version in your >> header, instead of including *.h >> That way, you can create safe history stacks and if the iop version has >> been updated, the iop legacy_params fct will update params. > How is this supposed to work since I'm using the current active iop? The > version is the one that is loaded in Darktable. Or I'm missing something? > yes but this version can change. The principe here is drop the include "iop/....h" and you replace it by duplicating the iop params structure. You add it to lightroom header as well as the iop version you pick the struct from When you save all that in the db, be carrefull to save the iop version too, even if it's not the current one. That way, the next time the user load the history, params will be automatically updated. >> boucman propose to add some assert statements... > We already have checks, but I probably do not understand what is proposed... He propose to add asserts to drop params inclusion if an error occurs > BTW, where all this is discussed as it seems I'm missing lot of > interesting and important discussions! We just had this discussion on IRC (#darktable) > Pascal. > Aldric
------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
