Почему в Лазарусе до сих пор нет заголовочников для GDI+ / Gdiplus / GDI Plus ?

[MinGW2018]

Вот пишу я тут кое-что для Windows - понадобилось использовать [ GDI+ | Gdiplus | Gdip | GDI Plus ] - а его и нету!
Да мне и не нужны обёртки в виде всяких классов/интерфейсов, мне нужен только Flat GDI+! Объявления типов, макросов и функций. И всё!
Это же часть WinAPI! Почему нету заголовков?!

[Handoko]

Hello MinGW2018,
Welcome to the forum.

OP's post translated using Google Translate:

Here I am writing something for Windows - I needed to use [GDI | Gdiplus | Gdip | GDI Plus] - and it's not there!
Yes, I do not need wrappers in the form of any classes interfaces, I need only Flat GDI! Declarations of types, macros, and functions. And that's it!
This is part of WinAPI! Why are there no headlines ?!

Maybe this links can be useful for you:
https://forum.lazarus.freepascal.org/index.php?topic=6423.0
https://forum.lazarus.freepascal.org/index.php?topic=22085.0
http://wiki.lazarus.freepascal.org/fpGUI

[ASerge]

[ GDI+ | Gdiplus | Gdip | GDI Plus ]

GDI+ Library

[MinGW2018]

Hello MinGW2018,
Welcome to the forum.

Hello! Many thanks!

I am writing something for Windows - and I need to use [ GDI+ | Gdiplus | Gdip | GDI Plus ] - and there is no headers in Lazarus!
I do not need classes/interfaces wrappers. I need only "flat GDI+"! Declarations of types, macros, and functions.
This is part of WinAPI! Why are there no headers?!

Please, add it into LCL!

Topic: 6423.0: GDI plus in Lazarus? - dead link.
Topic: 15746.0: Is it possible to uses GDI+PLUS With lazarus? - no information.
Topic: 22085.0: GDI+ Library - dead link & old attach.

[sash]

> Это же часть WinAPI! Почему нету заголовков?!

Потому и нету (я так думаю), что код который работает только на Windows, для Lazarus (являющийся кроссплатформенным) являет малую ценность/приоритет. Так, только в качестве дополнения, в частном порядке, и уж никак не в LCL.


Handoko дал тебе ссылки на темы, там есть вложение .rar, обнови, дополни, выложи, поможешь другим заинтересованным.

P.S. А зачем тебе вообще gdiplus?

[marcov]

I do not need classes/interfaces wrappers. I need only "flat GDI+"! Declarations of types, macros, and functions.
This is part of WinAPI! Why are there no headers?!

It is not. "GDI" is winapi, GDI+ is an additional library introduced with Windows XP.

GDIplus mostly adds some multimedia handlers, and is notoriously slow and buggy. What is so crucial in GDI+ that you need it? And why don't you just use it together with the GDI backend, why must the whole backend be GDI+ (which IMHO is not very realistic)

Please, add it into LCL!

The LCL is a GDI backend library.

Topic: 22085.0: GDI+ Library - dead link & old attach.

(I assume you mean this attach: https://forum.lazarus.freepascal.org/index.php/topic,22085.msg129802.html#msg129802 )

So what that it is old? So is gdiplus?

[taazz]

Topic: 22085.0: GDI+ Library - dead link & old attach.

that old attach works perfectly for me. I'm using it to add support for gdi+ in a number of components. Did you tried it and had problems?

[MinGW2018]

It is not "additional", it is "OS subsystem". Yeah, it is "new library introduced...". But it is OS part. Just new part. Like "Userenv.dll", like "Magnification.dll", like "Advapi32.dll".
Contrariwise, function AlphaBlend() or GradientFill() is not part of GDI32, it is from additional library "Msimg32.dll" introduced with/for IE. But it is declared in Lazarus.


Didn't get your words about together/realistic, sorry.

and is notoriously slow and buggy.

erm... GDI+ is not slow. GDI32 is slow. I have checked. Also, GDI+ supports highest quality than GDI32.
I have ever faced the only one bug: with GdipCreateHBITMAPFromBitmap() from a JPG image.

So what that it is old? So is gdiplus?

GdipBitmapConvertFormat() - not declared.
GdipBitmapApplyEffect() - not declared.
GdipDrawImageFX() - not declared.
GdipCreateEffect() - not declared.
e.t.c.

[marcov]

It is not "additional", it is "OS subsystem". Yeah, it is "new library introduced...". But it is OS part. Just new part. Like "Userenv.dll", like "Magnification.dll", like "Advapi32.dll".

Well, afaik gdiplus was meant to be the graphical backend of Winforms originally. That's why it contains duplicates with GDI while those other subsystems that you name do not.

Contrariwise, function AlphaBlend() or GradientFill() is not part of GDI32, it is from additional library "Msimg32.dll" introduced with/for IE. But it is declared in Lazarus.

If you look carefully, it is declared in Jedi libs, not in the core headers.

and is notoriously slow and buggy.

erm... GDI+ is not slow. GDI32 is slow. I have checked. Also, GDI+ supports highest quality than GDI32.
I have ever faced the only one bug: with GdipCreateHBITMAPFromBitmap() from a JPG image.

I do have to confess most of my experience was from XP times.

Anyway, I checked if there is a 3rd party Delphi project that translated the header, but unfortunately it has an incompatible header (BSD with advocacy clause). http://www.bilsen.com/gdiplus/index.shtml

[Thaddy]

I did one for KOL. Still works.

[MinGW2018]

... it is declared in Jedi libs, not in the core headers.

So... Let's paraphrase my "Please, add it into LCL!" as "Please, add it into Jedi libs!". 

Also, I can't find a lot of "Interfaces" in Lazarus... For example, IShellItemImageFactory...

..., but unfortunately it has an incompatible header (BSD with advocacy clause). http://www.bilsen.com/gdiplus/index.shtml

Thanks! A'll check it!

I did one for KOL. Still works.

Is it "GDIPVER>=0x0110"? Where can I get the latest version? Thanks!

[Thaddy]

I did one for KOL. Still works.

Is it "GDIPVER>=0x0110"? Where can I get the latest version? Thanks!

There isn't any and I will not update it. But it still works. It is highly stable even on Windows 10.+
Reason: Time and lost interest in KOL -because Vladimir Kladov dropped development and support -. Although I will answer KOL questions....