It has just been commited into SVN repository.
I hope it works OK because I haven't had much (any) time to test it yet.

Good idea. I think it could be done like this:

function LoadGLTextureFromFile(const FileName: string; Width: PLongInt = nil; Height: PLongInt = nil): GLuint;
begin
  ... create texture ...
  if Width <> nil then
      Width^ := CreatedWidth;
  ...
end;


This way users that don't care about created texture's dimensions (like when you use it as regular texture mapped on 3D object) wouldn't need to give the function more parameters (like with var parameters) and those who need it can get it. No need to add it to SDL functions too as they return pointer to structure which already contains surface's width and height.

Thanks for support.
Any new features you would like to see in future versions of Imaging?

I've looked at those images you sent and problem is probably caused by this:
Data format is A1R5G5B5 but that A1 bit is always set to zero. DisplayImage
shows image OK because it doesn't do any alpha blending. On the other hand,
you probably have alpha blending enabled in your OpenGL app and because
whole alpha channel of image is zero you don't see anything (try to disable
blending in OpenGL to see if there is any change). 
You could use X1R5G5B5 or R5G6B5 data format if you don't need alpha
or just set that A1 bit of A1R5G5B5 image to 1.

Please let me know if any of this helped (or not helped).

JPEG2000 support for Imaging is working quite well. It uses
OpenJPEG library written in C compiled to object files (that is
the reason why it won't be included in library core - no native Pascal).
It works with Delphi (C lib compiled by C++ Builder) and Free Pascal
(C lib compiled by Visual Studio 2005).  It is Win32 only now but I hope I will
manage to get it working in Linux soon.

I am working on package with extra content for Vampyre Imaging
Library. That means additional image file formats, new extensions,
demos, and other stuff. 

File formats in extras will also include JPEG2000. Reason why it won't
be in the core library is this: there is no native Pascal library for loading/saving
JPEG2000 images (at least I haven't found one) so Imaging will link to
C library compiled to object files (openjpeg most probably).
Therefore it won't work on all platforms supported by Imaging (and thus cannot be
included in core library).

There is also PCX loader, there will be PNM (for PBM,
PGM, PPM, and PAM) loader/saver, and maybe even GIF
support (if there will be enough time to implement it).
I have converted my old Daggerfall image/texture loaders to Imaging too
and added Redguard and BattleSpire support.

First version of extras package will be released around the end of 2006.
New Imaging release will be made too because stuff extras depends on some changes
made in core library since 0.20 release.
Current working version of Imaging and extras package is in project's SubVersion repository.

Visit Vampyre Imaging Library homepage

Imaging now uses SubVersion repository instead of CVS.
All new source changes will be commited there.
CVS still works but it won't be updated.
Look here for Imaging's SVN info: http://sourceforge.net/svn/?group_id=125626

Version 0.20.0 of Imaging has been released!
New features are in and many bugs found in 0.18 has been fixed.

Main news/changes in 0.20.0:

• New TImagingCanvas class with methods for drawing objects
  and applying effects was added (although there is not much functionality yet).


• New image data formats based on 16bit half-float (FP16) type has been
  added and OpenGL and Direct3D extensions can now create textures
  in these formats too.


• Imaging now compiles and works on 64bits CPUs (Linux on AMD64). 


• High level interface classes were extended and updated as well as VCL/CLX/LCL
  support and low level interface. 


• Some old demos were removed, new added, and rest was updated.

For downloads and documentation visit project's homepage at:
http://imaginglib.sourceforge.net