lzRichEdit did not install in 1.6

[bill0287]

I downloaded the sourceforge version of lzRichEdit and tried to install it in Laz1.6 (win32 version) and got this error:

Code: Pascal  [Select][+][-]

1. Compile package LazRichEdit 0.1.5: Exit code 1, Errors: 1
2. gtk2wsrichbox.pas(41,29) Fatal: Cannot find Gtk2Proc used by Gtk2WSRichBox. Enable flag "Use Unit" of unit Gtk2Proc in package LCL.

any ideas?

[taazz]

as the message says you open the package lcl, locate the file name gtk2proc in the project inspector right click and select use unit. REbuild everything and you should be fine.

[bill0287]

Taaz, I am sure your description makes perfect sense to most, but I can't figure out what to do with it.

I open the lpk, and when I try to install it, I get that error.  I am not sure how/where to "open the package LCL."

I have installed this component before in older versions of Laz without this issue.   

[skalogryz]

I have installed this component before in older versions of Laz without this issue.

maybe it's time to switch to RichMemo?

[bill0287]

Is RichMemo as good or better than RichEdit?

[taazz]

Taaz, I am sure your description makes perfect sense to most, but I can't figure out what to do with it.

OK, what you do not understand? The open the lcl package part? you know there is an lcl.lpk that you can open right? In my 1.4.4 installation it can be found in <install directory>\lcl\interfaces.

[wp]

I downloaded the sourceforge version of lzRichEdit and tried to install it in Laz1.6 (win32 version) and got this error:

Code: Pascal  [Select][+][-]

1. Compile package LazRichEdit 0.1.5: Exit code 1, Errors: 1
2. gtk2wsrichbox.pas(41,29) Fatal: Cannot find Gtk2Proc used by Gtk2WSRichBox. Enable flag "Use Unit" of unit Gtk2Proc in package LCL.

any ideas?

Why does lzRichEcit require gtk2 units under Windows? Looks like a package issue. I can confirm this compilation error with Laz 1.6, but also with Laz 1.4.4 --> nothing related to Laz 1.6.

And: I would not take the disadvantages of modifying a standard Lazarus package (LCL) for fixing a broken package.

[skalogryz]

Is RichMemo as good or better than RichEdit?

It's exactly the same, since both are using the exactly same system provided controls.

[polpero]

My copy of lzRichEdit worked with the 2 previous releases of 1.6 (on windows)
But it won't install now...

///

Removing those files for Gtk2 from the package solves the problem...

[Pancetto]

No, removing Gtk2-packages doesn't help. More times verify by me! There ara several errors with "illegal type conversion: LongWord to TStream" a.s.o. (unit Win32WSRichBox).

Other resolving for the problem?

[skalogryz]

Other resolving for the problem?

try RichMemo. Don't forget to add RichMemoHelpers to your uses section, to make RichMemo more delphi compatible (as lzRichEdit does)

[polpero]

Pancetto

Can you give me examples of the offending operations?
I can't yet replicate those error messages you state.

thanks

[bill0287]

I opened the lzrichedit lpk and unchecked "use unit" for these three files and the component installed on windows, but the included demo would not compile.

interfaces/gtk2/gtk2wsrichbox.pas
interfaces/gtk2/gtk2wsrichboxfactory.pas
interfaces/gtk2/gtk2rtftool.pas

[wp]

Here the compiler complains about a missing JvHtmlParser unit. I just removed the reference to it, and luckily the demo compiles.

But note that your way of solving the package compilation issue with the gtk2 files is just a work-around. If you'd once decide to compile your program for gtk2 then you'd have to modify the package again. That's not good.

Switch to RichMemo, I did not have any issues with it. Or contact the author of the component ("typo").

[Pancetto]

Pancetto

Can you give me examples of the offending operations?
I can't yet replicate those error messages you state.

thanks

In the meanwhile I remove the dependencies for gtk2 in the install package of lzRichEdit as suggested, now it compiles an the error message isn't anymore. I've not yet tried to check my former progs with the component, if so I'll report this here.