json goes RichMemo

[rvk]

...
There are no open issues regarding TRichmemo that I am aware of....

There is a bug tracker which is aware, I have filed a bug report in January, but nothing seems to be handles in the last 3 years.

Your quoting seems to be wrong here...

But I can't find any open issues in the bug tracker for TRichmemo.

[CM630]

Hm, are we talking about the same bug tracker?
https://github.com/skalogryz/richmemo/issues

Here is a bug report:  https://github.com/skalogryz/richmemo/issues/13

[rvk]

Hm, are we talking about the same bug tracker?
https://github.com/skalogryz/richmemo/issues

Here is a bug report:  https://github.com/skalogryz/richmemo/issues/13

That's not the "bugtracker".
The bugtracker is here https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues
(See the link at the left of every forum-page which says bugtracker)

Not sure if anyone sees the issue page you're pointing at.

[dsiders]

Hm, are we talking about the same bug tracker?
https://github.com/skalogryz/richmemo/issues

Here is a bug report:  https://github.com/skalogryz/richmemo/issues/13

That's not the "bugtracker".
The bugtracker is here https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues
(See the link at the left of every forum-page which says bugtracker)

Not sure if anyone sees the issue page you're pointing at.

Bugs in TRichMemo would not be reported to the Lazarus bug tracker. It is a separate package, and not part of the LCL.

[rvk]

Bugs in TRichMemo would not be reported to the Lazarus bug tracker. It is a separate package, and not part of the LCL.

Sure, but one shouldn't call the issue page of individual components "the bugtracker" here on the forum then

[Hansvb]

As a reply to the first post.

Parsing to a string, - is even harder. I failed so many times and lost information and read error-messages...

I also happen to be working on json and am trying out a few things beforehand. The code in the zip file is still very premature but the basics works.

• The json is put in a treeview. Completely copied from the json example that comes with Lazarus.
• The Json is put in a memo.
• The json is put in a stringgrid. (I will leave this I think)
• The json is put in a dataset so that this dataset can be linked to a dbgrid. (better option because I also want to sort and filter later).

It is a trial/error created file, any comment lines are in Dutch. In the print screen you can see what it can do so far. This is the json from post 1 (slightly improved first).

[Thaddy]

There is a jsonviewer in the tools section with full sourcecode.
lazarus/tools/jsonviewer.

[Hansvb]

I know:

Completely copied from the json example that comes with Lazarus.

[Thaddy]

It is not one of the examples. It is a complete tool.
That made me think you were not aware of it. The examples are separate.
The examples are in fpc/packages/fcl-json/examples
I also lift code from the tool....

Nit-picking, yes..