Ah, "under development" ?
OK, that explains it I guess. Might be a good idea to document that on the Wiki, I assumed it was mature and have spent a long time trying to work out what I was doing wrong.
well, it's kinda reverse.
If you find a method in TRichMemo, that is not documented on the wiki, then consider it as an experimental feature.
There are a few: SetLink(), InDelInline() and Print().
SetLink is probably the closest for the "release".
Feel free to create a new wiki page or use an existing one, like
RichMemo/Features or
Internals. (The main RichMemo page got pretty big, it should be split apart)
But, in the case of OnLinkAction, I guess I need make a workaround. Looks like the call back works, I can easily find the extent of the link.
SetLink, should be working just fine for Win7 and later. Thus Win8 and Win10 should work.
On WindowsXP it's possible to make it work, but requires lot more efforts.
So, does this mean the other problems I have been having are 'real' too ?
I'd think so.
Richmemo follows painware or complainware development model.
I rarely do anything for it to work, but typically tracking anyone start complaining/bug reporting about it.
Once there's an issue, it's being addressed. If I'm lucky, the person reported the issue is still around and can do a good through test of a feature fixed.
(Here's
an example of "complain" that typically sparks my interest. It's not directly RichMemo related. However TRichMemo inherits from TMemo, and thus inherits erratic behavior as well. As you might see, TC didn't stay long enough, thus no actions were taken)
Should I be putting in bug reports (on bug tracker, under CCR) ?
bug reports and/or patches are always welcomed on the bug tracker.