Question [LAB] Cindy components

RockyLuck wrote: @Viking: your assumption that the message to catch was CN_DRAWITEM was understandable, probably this should have happened, but it was not correct. This is the code for handling the WM_DRAWITEM in function WIndowProc (file Win32callback.inc):

I just had another quick look at pl_Cindy package.

More CN* and CM* messages are incorrectly translated as LM* messages! Some inherited calls that are required are commented out. I would start from there.

I installed CT on Windows 7 x64 in VirtualBox so I can check some of the samples there.

Would you please compile some of the samples included in CodeOcean with Delphi and post some screenshots? I need to see how those components should look when work properly in order to try to fix them.

viking wrote: More CN* and CM* messages are incorrectly translated as LM* messages!

They are only translated "incorrectly" because Lazarus does not correctly translate them into CN messages. That's no fault on behalf of the pl_Cindy package.

This is the image of the cyAdvButton demo when compiled with Delphi 7:



Hope this helps

RockyLuck wrote:

viking wrote: More CN* and CM* messages are incorrectly translated as LM* messages!

They are only translated "incorrectly" because Lazarus does not correctly translate them into CN messages. That's no fault on behalf of the pl_Cindy package.

I was talking about wrong code conversions done by someone from CT team while converting Cindy to Lazarus.

I was talking about things like this:

For example in cyBaseSpeedButton.pas

there is
procedure CMMouseEnter(var Message: TLMessage); message LM_MOUSEENTER;
instead of
procedure CMMouseEnter(var Message: TLMessage); message CM_MOUSEENTER;

Also
procedure CMMouseLeave(var Message: TLMessage); message LM_MOUSELEAVE;
instead of
procedure CMMouseLeave(var Message: TLMessage); message CM_MOUSELEAVE;

In
procedure TcyBaseSpeedButton.CMMouseEnter(var Message: TLMessage);

Inherited; is commented, but it is needed there.

... and so on.

RockyLuck wrote: This is the image of the cyAdvButton demo when compiled with Delphi 7:

Hope this helps

Thank you. That is what I was looking for.

sternas wrote: Thanks Sir
we will fix these problems

I do no use those components, so I only write about things that I noticed while checking what is done. I also would suggest to convert latest version, since I also noticed that this is not the latest version.

I am not sure that those changes that I mentioned will make all components work like in Delphi, but I hope that at least some of them will start to work better (or even as they planed to work).

Cindy v5.03 released!

Added TcyBook component:
https://sourceforge.net/projects/tcycomponents/screenshots/328505
Virtual book with turn page effect (perfect for android devices), page rendering etc ...

Also added TcyBook and TcyDebug demo.

Mauricio

what are the ETA for 2.80?

sternas wrote: Sir
ETA for ver 2.80, 5-6 days
if all lab tests are OK

1. What about the glyph problem for some buttons as reported in this thread?

2. Can you tell which Cindy components will only work on Windows systems?

Thanks

Thank's by all

If I remenber well I use Pascal the first time with delphi 2
I try to help you sometime in the future

sternas wrote: Sir
Our opinion is that, these are small problems.

Please don't forget that
CodeTyphon Studio is a free project
and it's not a company product, we don't have customers...

I understand that. The questions were not meant as criticism. They were just questions

The cyAdvButton problem is not a small problem, if you want to use the cyAdvButton in a project. It just does not work. Again: no criticism, just an observation.

The question to be able to plan my projects: is that problem solved in release 2.80?

Which brought me to the next question: which packages or which components are not portable? In the current state, the cyAdvButton is not portable, because the WM_DRAWITEM message is not provided by the Linux implementations of Lazarus. If I want to produce a completely portable program, which components should I avoid?

Maybe, in the Lazarus' components directory, in the next release, you could add a file to describe that.

sternas wrote: With this philosophy, some errors will exist.
and we can work together to solve these issues.

I agree and I did: I already supported you guys by providing the missing skins for the Lava package.

It's just that the cyAdvButton problem is too complicated for me.

Regards ;-}
Dick

Cindy V5.05 released!

Big improvments (speed up using windows gdi) made in TcyBook component!

Cindy components V5.05
15/07/2012 - cyBook.pas - We can see now page behind on the turn page effect!
14/07/2012 - cyBook.pas - Small bugs fixed + improvments
14/07/2012 - cyBook.pas - Despite it is not coherent in real book, we can set page with odd (1,3,5 etc ...) numbers to CurrentLeftPage property
13/07/2012 - cyBook.pas - Added TTurnPageAnimation.DoubleBuffered: Boolean property
13/07/2012 - cyBook.pas - Replaced use of BitmapResize() that is too low by DrawCanvas()
12/07/2012 - cyBook.pas - Removed prFitMediumQuality and prStretchMediumQuality to TPageRender
12/07/2012 - cyBook.pas - Modified BeforePreparePage event in order to able custom page rendering or/and use external page resizing engine.
12/07/2012 - cyBook.pas - Added OnLeftPageClick and OnRightPageClick events
12/07/2012 - cyProgressionPanel.pas - Added property State to public declaration
12/07/2012 - cyAdvProgressionPanel.pas - Small bug fixed on .Open procedure (avoid error if we call several times open()
12/07/2012 - cyAdvProgressionPanel.pas - Added property State to public declaration
11/07/2012 - cyBook.pas - Some optimization and added read/write property access to TBookPageView (for exemple TBookPageView.Page: TBitmap)
11/07/2012 - cyBook.pas - Turn page with mouse if page dragged and not clicked
11/07/2012 - cyBook.pas - Added DblClick event
11/07/2012 - cyBook.pas - Added boFitSmallImages and boStretchSmallImages to Options

Regards,
Mauricio

I have changed to HALFTONE myself after checking that quality is the same.

"I think now cybook is OK "
You bet!

Regards,
Mauricio

There's a couple of bugs in cyAdvSpeedButton.pas. The bugs are all of the same nature: if a test is made against the State of the TcyAdvSpeedButton the state "bsHot" is always forgotten, resulting in an exception as soon as the cursor hovers over such a button.
The bugs can be fixed as follows:

Lines 408-409: case FState of bsUp {Add this:}, bsHot: {this one is less important}
Lines 493-494: case aState of bsUp {Add this:}, bsHot:
Lines 578-579: case aState of bsUp {Add this:}, bsHot:

Especially the last two generate an exception because the RenderProp, resp. PaintButton are not assigned!
This bug was already reported in #2094

The same bug would surface in cyAdvButton in the DrawButton and DrawBackground procedures, but these procedures are never called, because of the other bug ( #1796 ) which has been declared minor ( #2242 ) (although the cyAdvButton is completely useless because of it).