LazPaint (alpha-blending, antialiasing, filters)

[Dibo]

Ok, I found it. My component package did not have "LCL" package in require section. Now everything works . I publish this components soon.

[circular]

Cool. If I understand, it's a replacement for TImageList. But does it change the rendering of toolbars ?

[Dibo]

Exactly. Teeview too.

[Dibo]

Ok. I created patch in bugtracker. I publish component when patch will be accepted. Sneak peak in attachments (before / after)

[circular]

Nice 

[circular]

Hello people, here is a new version (2.6) of LazPaint :
- fast blur and other blurs optimization
- water and perlin noise in filter menu

It is available as a zip file and on subversion.
https://sourceforge.net/projects/lazpaint/files/lazpaint/

I'm thinking about adding phong shading as a tool in LazPaint.

[Dibo]

I'm wondering, maybe you can create BGRABitmap classes as external lazarus package? I must always include BGRABitmap files into my BGRAImageList component. If I don't include then user must select path to lazapaint folder in BGRAImageList package options.
If BGRABitmap will be as lazarus package then I could add it as requied package in my package and don't need copy sources. It will make BGRABitmap more accessible for other components.

[circular]

Ok, I only need to create a lpk file ?

[Dibo]

I guess so. I crated my like in this article:
http://wiki.lazarus.freepascal.org/How_To_Write_Lazarus_Component

[Chronos]

Definitely it should be distributed as lazarus package. If someone want to include files itself in it's project it can.

This graphics library is impressive as I was digging deeper to it's internals I found many interesting algorithms.  

But recently I was trying to squeeze bitmap on screen rendering to the max and Drawing to visual component Canvas is fastest method. I would rather see direct copy internal data to target bitmap rawimage. As FBitmap with RawImage is already contained in TBGRADefaultBitmap it could be redirected directly to TImage.Picture.Bitmap and keep internal bitmap data associated with external component. It would be better to eliminate unnecessary copy operations.

[circular]

Definitely it should be distributed as lazarus package. If someone want to include files itself in it's project it can.

Ok. I found how to make a runtime package, so it can be used without compiling Lazarus. But, is it necessary to make a design package in order to use it on components ?

But recently I was trying to squeeze bitmap on screen rendering to the max and Drawing to visual component Canvas is fastest method.

I don't understand.

I would rather see direct copy internal data to target bitmap rawimage.

What code do you suggest ? Which methods would be changed ?

[Dibo]

Ok. I found how to make a runtime package, so it can be used without compiling Lazarus. But, is it necessary to make a design package in order to use it on components ?

I have no such knowledge about lazarus packages but there is a lot of packages which have no components on components palette (e.g. dcpcrypt, manualdock) so I think this is acceptable practice to create package without components.

[circular]

Yes, and it works. It's on subversion. But I wonder if I should check "Design and runtime package".

Now, only "Runtime package" is checked so it cannot be compiled into Lazarus. It is faster thus to update. But I do not know what happens if you want to use it with a component.

[Chronos]

I referred to wiki page http://wiki.freepascal.org/Fast_direct_pixel_access#TBitmap.RawImage where TImage can be used on form instead of Form canvas or PaintBox canvas which needs to be repainted by OnPaint event. It would be even faster you would store bitmap data in same format in your internal data and in on screen image bitmap data. Then simple Move would be used instead of slow for cycle. But in this case you can directly map TImage bitmap rawimage data as your internal data and then your class would work like wrapper. But rawimage data is platform dependent so it needs to be tested and properly handled.

Question is for what purpose you have FBitmap and LoadFromBitmapIfNeeded if it is not possible to use own bitmap in place (no setter for Bitmap property). You have already FData, FWidth, FHeight and BGRA pixel format.

[circular]

The base data structure is BGRA data. When you access to the Bitmap property, it is converted to a TBitmap for convenience. You can make changes to the Bitmap canvas, but then it must be updated to the BGRA data.

There are two possibilites :
- either a DIB section is possible which means that a TBitmap can be mapped directly to the BGRA data.
- or it's not possible or not implemented, then there is a copy between BGRA data and Bitmap handle. In this case, LoadFromBitmapIfNeeded loads the data from the Bitmap handle. And InvalidateBitmap signals that the TBitmap object must be built again, that the Bitmap handle is no longer updated.