[Solved] lzRichEdit

[JSN]

I have installed the component lzRichEdit. The example included loads from a file and saves to a file. I need to be able to load/save RichEdit content within a table in Firebird.

Is there a Tutorial that loads and saves lzRichEdit content within a table?

Lazarus Version 1.2.4
Firebird Version 2.5.3.26778.0

[JSN]

In addition to needing an example or tutorial on how to read/save RichEdit content to a database, I need to change the Color of TlzRichEdit. I tried Typecasting TlzRichEdit and nothing I do is changing the color. Obviously I am not a component writer.

Can someone help me with read/save RichEdt content to database and changing the Color of TlzRichEdit?

[typo]

Can someone help me with  changing the Color of TlzRichEdit?

Here an example:

Code: [Select]

SendMessage( lzRichEdit1.Handle, EM_SETBKGNDCOLOR, 0, RGB( 123,43,143 ) );

or

Code: [Select]

SendMessage( lzRichEdit1.Handle, EM_SETBKGNDCOLOR, 0, ColorToRGB(clYellow) );


[JSN]

Where is SendMessage defined?

[typo]

On Windows unit, but you can find it by yourself by right-clicking the compiler message and choosing Find Identifier.

[JSN]

If I include Windows in the uses clause, it reports a Syntax Error on "ClientToScreen(Point(X,Y));". Without Windows, "ClientToScreen(Point(X,Y));" compiles as expected. What gives?

[JSN]

If I right-click SendMessage when it doesn't compile, I click on "Find Declaration" and nothing happens.

What am I doing wrong? Why does a simple call to change a component color have to be rocket science?

[typo]

State Point like this:

Code: [Select]

ClientToScreen(Classes.Point(X, Y)); 


What am I doing wrong? Why does a simple call to change a component color have to be rocket science?

You are doing nothing wrong, the problem is that BackgrondColor is not implemented yet on lzRichEdit.

If I right-click SendMessage when it doesn't compile, I click on "Find Declaration" and nothing happens.

A dialog box should appear (not modal).

[JSN]

Thank you very much, Typo, that works beautifully. Still scratching my head, but thank you for holding my hand.

[typo]

On the loading/saving from/to database matter, perhaps this can help:

http://stackoverflow.com/questions/4074383/loading-rtf-text-from-database-into-trichedit

You can see a loading/saving example from/to a Memo control in the zip file attached.

[JSN]

Thank you for the link and example, Typo. I will be studying all of this information and then try to implement it into the appI am working on. I'll let you know what results I get.

Thanks, again.

[rvk]

If I include Windows in the uses clause, it reports a Syntax Error on "ClientToScreen(Point(X,Y));". Without Windows, "ClientToScreen(Point(X,Y));" compiles as expected. What gives?

B.T.W. instead of putting Classes. before Point (Like typo showed you) you could also put windows before Classes in the uses clause. The Windows-unit also defines a type named Point which conflict with the one from Classes. So if you put windows before Classes in the uses clause the Point of Classes is taken (instead of the one from windows). When having a big unit (or lots of units) this is an easier approach than changing all the Point's to Classes.Point.

[JSN]

On the loading/saving from/to database matter, perhaps this can help:

http://stackoverflow.com/questions/4074383/loading-rtf-text-from-database-into-trichedit

You can see a loading/saving example from/to a Memo control in the zip file attached.

Once I understood what was happening, your suggestion worked great. Thank you, Typo.

If I include Windows in the uses clause, it reports a Syntax Error on "ClientToScreen(Point(X,Y));". Without Windows, "ClientToScreen(Point(X,Y));" compiles as expected. What gives?

B.T.W. instead of putting Classes. before Point (Like typo showed you) you could also put windows before Classes in the uses clause. The Windows-unit also defines a type named Point which conflict with the one from Classes. So if you put windows before Classes in the uses clause the Point of Classes is taken (instead of the one from windows). When having a big unit (or lots of units) this is an easier approach than changing all the Point's to Classes.Point.

Thank you for the tip, RVK, I tried it and it works.