On 4/28/07, Paul Ishenin <[EMAIL PROTECTED]> wrote:
For me it is very difficult to create XPM for every new image I want
to add to lazarus. In windows I should at first create bmp or ico for
that purpose, then I must load my linux, start gimp and there to
convert from original image to xpm. It is not so fast and easy.
XPM has been around for many years and any half decent image editor
should be able to edit and save XPM files. Gimp is one such excellent
image editor and is available for Windows and many other platforms.
And it's free! :-)
formats). And why not to use modern and widely used PNG format?
PNG is supported by most of modern editors and it is possible to
I'm a big fan of PNG, but I don't know if all widget sets have PNG
support. Or the same level of PNG support. Some widget sets might
support reading the basic PNG image, but can't support it's alpha
bending (remember the issues with IE under Win9x), etc... PNG is quite
complex.
I think XPM was chosen due to the fact that in is a really easy format
and easy to implement on any platform or directly in the LCL. Open a
XPM file with a text editor and you will see what I mean.
GG> Palette Bar (component) images: 23x23
Should be 24x24 to be compatiable with delphi and thus to prevent
component developers of rebuilding their images (made for delphi).
I can't really say, I have seen many 24x24 size images in the
/images/components directory. If that is the correct size, then I
think we should resize the Palette Bar buttons slightly or something,
because under gtk1 when you mouse over 24x24 images they shift (jump)
to the right and down a few pixels and is very annoying. I testing
this under Win32 and there is no such problem. I haven't tested this
under gtk2 yet.
I have just submitted a patch a few days ago for a few images in the
Standard Tab, resizing them to 23x23 which prevented that shift
effect.
And then define somewhere constants with imageindexes. This also should help
lazarus to eat less memory and gdi resources (at least soon when our TImageList
become native).
I don't know if Lazarus uses TImageList's internally. I thought they
load images directly from the laz_images.lrs resource file using the
resource name. In that case, we must just let them both use the same
resource name. I tried that with my Lazarus and it works fine.
I create a new menu_save_16.xpm file and let both the menu item and
the button load the menu_save_16 resource image.
--
Graeme Geldenhuys
There's no place like S34° 03.168' E018° 49.342'
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
