Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Galfar

Pages: 1 2 [3] 4 5 6 ... 24
seems like the problem is not in GCC, or at least not in CPU architecture.

I did some experiments and the static lib (libtiff.a) produced by GCC is different
when you use "-arch i386" than with no flags. 64bit one is roughly 2x bigger in size
than 32bit one.

Also FPC gives this message:
ld: warning: ignoring file ./libtiff64.a, file was built for archive which is not the architecture being linked (i386)
when trying to link to x86_64 library.
This message is not displayed when linking library generated with "-arch i386".

Anyway, for both libraries linking always ends with:
Undefined symbols for architecture i386:
  "_TiffGetVersion", referenced from:

Maybe symbols are not properly exported or something :(

Help & Questions / Re: FireMonkey Demo
« on: 1 June 2012, 12:08:42 »
Does this mean, in your opinion, that Threads cannot be used reliably in FireMonkey Applications?  Makes it not exactly ready for prime-time!
Certainly seems like it. 

Yes, they were in those two latter libraries.  I assume I can safely ignore the warnings?
Yes you can safely ignore these warnings.

Help & Questions / Re: FireMonkey Demo
« on: 24 May 2012, 14:39:45 »
It happens sometimes, the problem is with TThread.Synchronize (TThread.Queue doesn't work at all) in FireMonkey app - the form is
not notified that the background thread finished loading the image.

Where exactly do you mean? In Imaging core AnsiString and AnsiChar are for a reason (loading from files etc.) but warnings shoudl not be generated by Delphi. There are some warnings in JpegLib and LibTiff libraries though.

Help & Questions / Re: Size of ImagingCanvas?
« on: 24 May 2012, 14:06:56 »

@canvas size:
the canvas always spans the entire underlying image so the size of canvas is the same.
You can restrict canvas operations to clip rect area (by default clip rect is the whole canvas/image
so you could get canvas width and height by Canvas.ClipRect.Right and Canvas.ClipRect.Bottom).

@fading effect:
you mean like gradient fade? If yes then merging the images would probably be faster than painting the gradient
itself. You would have background image and alpha blend a prepared image with some fading effect onto it.

@blend vs alpha:
DrawBlend is general function with custom blending parameters for source and destination pixels.
DrawAlpha and DrawAdd are just DrawBlend with specific parameters set to get the desired effect.
You can experiment with blendign parameters and see what you'll get :)

PS: I can't register at this forum - get error
Please try again now.

Help & Questions / Re: JPEG watermark
« on: 15 May 2012, 12:26:58 »

Could you please check if TIFFs with JPEG compression are working with TiffLib compiled for MacOS?

Help & Questions / Re: GIF Animated (ExtraGIF)
« on: 15 May 2012, 12:21:19 »

check out the attached
I had to make some fixes to ExtraGIF for it to work in D2009 and newer.

The problem with ExtraGIF is that it's 3rd party contribution based
on Imaging 0.26.1 so the old copy of some Imaging files was needed
(included in

PS: ImagingGIFLoadAnimated was added later than ExtraGIF and is not needed for it.

Help & Questions / Re: Upgrading from 0.22 to 0.26.4
« on: 17 March 2012, 17:12:42 »
dglOpenGL is still being updated so new OpenGL features are in (e.g. OpenGL 3/4),
I'm not sure if "GL, GLext" headers are. 
It doesn't matter if your game targets older hardware (where new OpenGL features are not supported
by HW anyway).

Help & Questions / Re: Upgrading from 0.22 to 0.26.4
« on: 15 March 2012, 20:35:11 »
You can configure ImagingOpenGL to use "Gl, Glu" instead of "dglOpenGL headers if that's what you are using in Mundo.

News & Announcements / Re: Next update info: 0.78
« on: 8 March 2012, 02:26:19 »
New release 0.78 just needs two more bug fixes to be finished and it will be ready
for final testing. There's also quite a lot of documentation to be updated.

Help & Questions / Re: Upgrading from 0.22 to 0.26.4
« on: 29 February 2012, 02:54:20 »
Hi Rodrigo,
could you provide some details about compiler and OS you use for Mundo?
Maybe there could be some problem with code in "initialization" section in Imaging in your OS+compiler combination.

News & Announcements / Re: Next update info: 0.80
« on: 31 December 2011, 02:04:28 »
Hi, that's what I'm planning now. Stay tuned just a little bit longer please :)

Thanks for the report, fixed.

Bug was found and fixed. GTK2 uses different RB order than Win/Qt/Carbon widget sets and it
wasn't checked when converting from LCL bitmap back to Imaging. I'll update repository tomorrow.

Basically, LCL/VCL stuff was added to get ability to simply display Imaging's internal image formats
in GUI apps. If you just want to load/rotate/scale/save there's no need to use LCL stuff.

Btw, ifA32R32G32B32F seems like an overkill (128bits per pixel) that the file formats you use
for saving just convert back to 24/32bit.

Pages: 1 2 [3] 4 5 6 ... 24