XnView Software

Given my experience, loading an image with gfl is extremely simple, the lib will find all what it need int the file header. So, after loading default load parameters, try to specify this params.Flags only: You should specify the FormatIndex of the save parameters and then the compression, Compressio...

You should post this the XnView section of the forum
Here is the GFLSDK forum.

Not shure but I think the problem is while opening 16 bits images.
When I add text with gflAddText, the text is well added (color & position).
Hope it helps

More info:
Using 2.90 -> No problem
Using 3.11 -> Problem

Dear xnview, I'm trying to open and process 16bits TIFF images and got some problems. I tested this images on XnView without problem. I just got a message that said something like this : "the image will be open in 8 bits/channel...". Then I can save in 8bits/chanel without any problems I try to repr...

Hi,
You have information about metadata function in the wiki of GFLSDK, follow the link bellow:
http://www.xnview.com/wiki/index.php5?title=GFL_SDK

What happen if the gflLoadBitmap() don't succeed? Does the file info structure shouldn't be freed, is it?
Thanks

I tested the exemple you give and got no result. I do some visible watermarking with gfl and I use gflBitblt/gflBitbltEx instead of pixel per pixel copy. I guess gflMerge is built on this functions. Edit : I 've juste done other tests and got something interesting Try to use opacity between 0 and 10...

I have the same behaviour on a XP machine : we can't say how the OS choose to run a thread on a given core.

Hello, Here is something wrong, isn't it? fragment := gflAllockBitmap(gfl_bmp.BType, W-X, H-Y, gfl_bmp.LinePadding, @bgColorGFL); Should be fragment := gflAllockBitmap(gfl_bmp.BType, W, H, gfl_bmp.LinePadding, @bgColorGFL); to match with the cropRect ?

Hello,
Have you tried to remove/comment "unsafe" code : for exemple newest code, special memory allocation/delete... This kind of error is difficult to fix.
Help yourself with your debugger.
I don't think Pierre could help you without more information.

If you need some assistance you can search or ask for details in GFL forum.

You should becarful of the IFD in the EXIF functions. In the previous version 2.90, the IFD_0 and MAIN_IDF were REVERSED. You should use IFD_0 for resolution. See this link to choose the right IFD and the right type of value : http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/EXIF.html I think y...

I test this functions without this kind of error.
There might be something wrong elsewhere in your code ?
Do you test the same code in a small project with only this features ?

Hello,
You should post some code with wrong memory access so I can do similar tests
See ya,