Pascal, I just have done a quick look at your code. You add a button somewhere in darkroom, isn't it ? So you read xmp from darkroom mode and change iop params directly ? IMHO it's not the right place to do such stuff. AFAIK xmp importing/exporting is usually done in the "file manager" (or call it as you want ;) ) Why don't you add your button to the import/export module inside lighttable ?
Aldric Le 21/01/2013 22:39, Pascal Obry a écrit : > Aldric, > >> 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, > I save nothing into the db. There is probably a misunderstanding. > > Or are you saying that instead of creating the history in memory and > activating the module I should just drop information into the database > and ask at the end to reload the history? > >> He propose to add asserts to drop params inclusion if an error occurs > That's already the case as discussed with Johannes some days ago. > > Pascal. > ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
