XnView Software

please, can you send me the new "libgfl252.dll" for testing too?
thanks

luisribeiro@duasribeiras.com
I'll upgrade GFLSDK next week...

Wouldn't it be appropriate to do a beta/rc-testing-phase before official releasing the new version?

2.40 included a range of more or less trivial to fix bugs ...

Hiho,

All new stuff I write is designed to be unicode 'aware'.
Unluckily GflSDK itself is not.

Thus I wrote a simple layer to work around this problem.

Grab a copy here:
http://celebnamer.celebworld.ws/stuff/libgflW/
README
I added a simple Unicode layer. (see gflCUnicodeLayer.cpp/h)
This ...

Code looks like this:
GFL_ERROR GFLC_BITMAP::create(const GFLC_BITMAP & bitmap)
{
return create(bitmap.getType(), bitmap.getBitsPerComponent(), bitmap.getWidth(), bitmap.getHeight());
}

While it must be:
GFL_ERROR GFLC_BITMAP::create(const GFLC_BITMAP & bitmap)
{
return create(bitmap.getType ...

Can you determine the "stage" when corruption occures.
(eg. by setting CS arround gflLoadBitmap and/or gflSaveBitmap).
I think that would give Pierre a better clue.

(I know about the problems of debugging MT-code on a single processor box :p)

Something like:

#include <libgfl.h>
#include ...

What happens if you run this testcase program.
Its a console application which expects first argument to be the file ;))
(You'll propably need to set appropriate #pragma link)
(Maybe doing <iostream.h> inststead of <iostream> but anyway)


I can verfiy that output is correct with BCB6 and MSVC.NET ...

Strange anyone has the same problem?

Question is: how do you get the value?
something like ftell();
or maybe GetFileAttributesEx()?
Latter has some issues when computing the size the wrong way. But can not fully recall what was causing them...
have to look in my code archive...
(and this issue ...

Solution is simple. (As long as this is indeed the reason).
LinePadding member of is initilized to 4 (2.20+) while it was prior 1 (2.11)
Change it back to 1 manually after call to gflGetDefaultLoadParams. ;)

Right, now the padding is 4, better for windows compatibility...
I know.
But I think ...

Anybody (like Pierre eg.) able to confirm?
Any work on this issue in progress?

Solution is simple. (As long as this is indeed the reason).
LinePadding member of is initilized to 4 (2.20+) while it was prior 1 (2.11)
Change it back to 1 manually after call to gflGetDefaultLoadParams. ;)

test it yourself:
#include <windows.h>
#include <stdio.h>
#include <iostream>
#include ...

On XP (SP1 still) (and using CBuilder6) Im getting AVs in subsequent calls after using gflAutoCrop like this:
gflAutoCrop(BMP, NULL, NULL, 85);
eg. calling gflResize afterwards thows an AV.

When using
GFL_COLOR c;
gflGetColorAt(BMP, 0, 0, &c);
gflAutoCrop(BMP, NULL, &c, 85);
such subsequent ...

Hi Pierre,
first thx for releasing v2.40.
Im currently doing my test with it :D

We talked some time ago in another topic about Borland CBuilder "incompatiblities" when it comes to #ifdef WIN32

Seems I forgot to mention another incompatiblity in libgfle.h
Using the same "scheme" you've taken for ...

Also you can change the zip compresion by 7zip.
7zip is under GPL, not free.

It is free, but maybe too free LOL

But actually you're wrong.
LZMA SDK is actually somwhat quad-licensed.
1.) GPL
2.) Common Public License
3.) "Unmodified Source" License
4.) Proprietary license (to buy)

Especially 3 ...

no french here.
anyway:
#include "libgfl.h"
#include <iostream>

bool verify(const char *act, GFL_ERROR err)
{
using namespace std;
bool v = err == GFL_NO_ERROR;
cout << act
<< ": "
<< (v ? "OK" : gflGetErrorString(err))
<< endl;
return v;
}

// use a pointer to a GFL_BITMAP pointer in order ...

I understand a little French, while I have a hard time to write in that language, hence Ill stick to English. :p

There is a problem in the header files which may cause BC++ to take some wrong defines that declare the calling convention.

The problem is that BC++ for some reason sees:
#ifdef WIN32 ...

I'd like to see the DEL key working for Folder-Tree as well.
DEL means: Delete folder

Wasnt sure where to post this, the RC forum or this thread?!?