KControls installation issue lazarus / 21-General ---------------------------------------------------------------------- bobonwhidbey · 2021-06-07 16:14 I downloaded KControls 1.7.3 and installed two packages:    KControlsBase    KControlsLaz Now,whether or not my program is using a KControl I get a warning message:   other unit files search path of "KControlsLaz 1.73 contains .... which belongs to package KControlsBase   other unit files search path of "KControlsBase 1.73 contains .... which belongs to package KControlsLaz Is there a way to stop getting these warnings, short of uninstalling the KControls packages? ---------------------------------------------------------------------- wp · 2021-06-07 16:31 As far as I can see from the package files, both packages have their associated units in the same folder. This is bad. Package source files should always be in separate folders. So, the package owner should "re-package" the units. Or somebody (you?) should clone the git repo (https://github.com/kryslt/KControls) and send the maintainer a pull request. But be warned: the maintainer wants to keep Delphi compatibility, so moving some source files to other folders will break the Delphi packages... ---------------------------------------------------------------------- bobonwhidbey · 2021-06-07 16:36 Thanks. Is there another package with something like a RichMemo that works well? ---------------------------------------------------------------------- wp · 2021-06-07 16:47 TRichMemo? https://wiki.freepascal.org/RichMemo. Maintained by one of the Lazarus team members. ---------------------------------------------------------------------- bobonwhidbey · 2021-06-07 17:44 I've downloaded lazarus-ccr-svn-r8048-components-richmemo. This package compiles but I can't install it. See attached. ---------------------------------------------------------------------- bobonwhidbey · 2021-06-07 18:56 There is only one package file in the downloaded:    RichmemoPackage.lpk It doesn't install in a "typical' way. Is there another way to utilize this component? ---------------------------------------------------------------------- Zoran · 2021-06-07 21:23 Quote from: bobonwhidbey on June 07, 2021, 08:56:15 pmThere is only one package file in the downloaded:    RichmemoPackage.lpk Look inside folder "ide". There is another package file -- richmemo_design.lpk. ---------------------------------------------------------------------- wp · 2021-06-07 21:28 Or you can also try the package in OPM, then you only have the usual 1-click installation. ---------------------------------------------------------------------- bobonwhidbey · 2021-06-07 22:29 Found that ...design.lpk and all seemed to install perfectly. Thanks. ---------------------------------------------------------------------- dbannon · 2021-06-07 22:54 bobonwhidbey, some comments that might help you choose between KControls and RichMemo. The warning from KControls does no harm, I have been using KMemo fo a number of years and see that warning all the time. Its just, as WP said, not a good idea in principle. Using TRichMemo will very much depend on your platform. Some things don't work on all platforms and on MacOS for example, quite a lot does not work.  Please see https://wiki.freepascal.org/RichMemo/WorkArounds The author of KControls has indicated he is not planning to develop KControls further but it is quite complete now. He is quite responsive to bug reports and does fix issues.  He totally replaced his license for example when I had issues getting my app into Debian because of his license wording. Sometimes RichMemo's maintainer is a bit slow to respond. From time to time I revisit RichMemo and submit patches but they can sit there for some time time. eg https://bugs.freepascal.org/view.php?id=37894 I find that KMemo becomes a bit slow when the content exceeds, perhaps 40K to 50K bytes.  I am not sure about RichMemo's responsiveness, not enough of it works for me to have tested with large content. However I suspect RichMemo would be faster on platforms where it works. So, as they say, your mileage may vary .... Davo