Lazarus

Programming => Packages and Libraries => RichMemo => Topic started by: dbannon on August 28, 2017, 02:42:07 pm

Title: RichMemo work arounds
Post by: dbannon on August 28, 2017, 02:42:07 pm
OK, as discussed a couple of weeks ago, I have made page on the wiki that documents the work arounds that I have found effective when using RichMemo.

http://wiki.freepascal.org/RichMemo/WorkArounds

Dmitry, I do hope you are not unhappy with my doing this but I do think that RichMemo is such a great component, it would be a shame if a potential user was frightened off by things not quite working as he/she expected.

I will try to keep that page up to date and would be very pleased if other users saw fit to add some tricks they have learnt. Especially if they improve on my ones, some of which I think are far from pretty !   %)

David
Title: Re: RichMemo work arounds
Post by: skalogryz on August 30, 2017, 03:20:47 am
ugh... some of the issues are indeed puzzling
Title: Re: RichMemo work arounds
Post by: dbannon on August 31, 2017, 01:35:07 am
"..ugh... some of the issues are indeed puzzling"

Oh, maybe. Some are easy fixes and some reflect the fact I'm pushing into space you have not yet declared open to the public !

The SetLink() needing unmarked up text and the refresh problem under Win, they sure are head scratching stuff .....

But I have a working system now and starting to show it to another open source project. I hope we'll be moving over to Lazarus in time.
Title: Re: RichMemo work arounds
Post by: ozznixon on June 25, 2018, 05:33:14 pm
Great Effort! Are these synchronized to the latest release?

As I find and resolve issues, I will be posting to the same Wiki.

PS. What is the official URL to TRichMemo?? I have found the copy I am running may not be the current build, as some of the examples people have posted in the RichMemo section do not work for me at all.
Title: Re: RichMemo work arounds
Post by: Ñuño_Martínez on June 25, 2018, 07:10:28 pm
Cool.

May be some (or all) these "work arounds" help TRichMemo developers to finish the component, may not?.
Title: Re: RichMemo work arounds
Post by: dbannon on July 05, 2018, 01:42:43 pm
Bit of a late answer, sorry about that chief.

I decided not to use RichMemo for my project, using instead KControls. This was a decision made mainly when I found a rather intimidating list of problems on the Mac. It seemed inconsistent with what I read on the main RichMemo page. Listed in the discussion section of the workaround page.

I also found it difficult to see if any further development was taking place with RichMemo, from memory, a new 'release' seemed to happen weekly but no changes seemed to be happening.

A pity really, its a much lighter weight package than KControls.

Davo