LazNodeEditor (visual node graph editor component )

[simsee]

The demo doesn't compile with Lazarus 4.6 yet. Can you test it with the current version of the IDE/compiler?

[wp]

Now the issue is "InflateRect(Result, 12.0, 12.0)" in TNodeGraph.GetLinkWorldBounds in LazNodeEditor.Graph. I wonder why you don't see all these issues? Sorry, I really don't want to be insulting now: but this sequence of posts reminds me of responses that I get when asking ChatGPT. Are you human?

[CynicRus]

Now the issue is "InflateRect(Result, 12.0, 12.0)" in TNodeGraph.GetLinkWorldBounds in LazNodeEditor.Graph. I wonder why you don't see all these issues? Sorry, I really don't want to be insulting now: but this sequence of posts reminds me of responses that I get when asking ChatGPT. Are you human?

Gentlemen, it never occurred to me that anyone was still using plain 3.2.2 — I had been working with 3.2 plus fixes. I’ve now specifically taken a clean, stable version, installed it on a VM, and fixed the build issue.
I use trunk for development and then backport the changes to an older compiler. Why trunk? Because I need its features for other code, and constantly switching compilers is inconvenient for me. For convenience, I’ve provided the current built codebase as a pre-release.
I apologize for the inconvenience. But as you can see, development is progressing very actively.

[simone]

Most users (myself included) are working with the current version of lazarus with the fpc build that comes with it. If you'd like to support this version, I'd be happy to test your component and provide feedback.

Now the issue is "InflateRect(Result, 12.0, 12.0)" in TNodeGraph.GetLinkWorldBounds in LazNodeEditor.Graph. I wonder why you don't see all these issues? Sorry, I really don't want to be insulting now: but this sequence of posts reminds me of responses that I get when asking ChatGPT. Are you human?

Gentlemen, it never occurred to me that anyone was still using plain 3.2.2 — I had been working with 3.2 plus fixes. I’ve now specifically taken a clean, stable version, installed it on a VM, and fixed the build issue.
I use trunk for development and then backport the changes to an older compiler. Why trunk? Because I need its features for other code, and constantly switching compilers is inconvenient for me. For convenience, I’ve provided the current built codebase as a pre-release.
I apologize for the inconvenience. But as you can see, development is progressing very actively.

[CynicRus]

Most users (myself included) are working with the current version of lazarus with the fpc build that comes with it. If you'd like to support this version, I'd be happy to test your component and provide feedback.

Now the issue is "InflateRect(Result, 12.0, 12.0)" in TNodeGraph.GetLinkWorldBounds in LazNodeEditor.Graph. I wonder why you don't see all these issues? Sorry, I really don't want to be insulting now: but this sequence of posts reminds me of responses that I get when asking ChatGPT. Are you human?

Gentlemen, it never occurred to me that anyone was still using plain 3.2.2 — I had been working with 3.2 plus fixes. I’ve now specifically taken a clean, stable version, installed it on a VM, and fixed the build issue.
I use trunk for development and then backport the changes to an older compiler. Why trunk? Because I need its features for other code, and constantly switching compilers is inconvenient for me. For convenience, I’ve provided the current built codebase as a pre-release.
I apologize for the inconvenience. But as you can see, development is progressing very actively.

Well, I’ll be more careful from now on and test things in both places before making an announcement Sorry again — I didn’t mean to cause any inconvenience.

[Dzandaa]

Hi,

@CynicRus:

Working now in Windows 10 with version 3.8 fpc 3.2.2.

Not teste in Lunix, yet.

I don't investigate more because lack of time, but I will.

B->

[CynicRus]

Hi,

@CynicRus:

Working now in Windows 10 with version 3.8 fpc 3.2.2.

Not teste in Lunix, yet.

I don't investigate more because lack of time, but I will.

B->

Hi! If you take the archive, then update the renderer.pas from main repo. Otherwise there will be an issue with getlock.

[simone]

The demo currently on GitHub compiles without problems now, but a run-time error (access violation) occurs if you insert a new node into, using the context menu (Add Node -> Default Node).

[CynicRus]

The demo currently on GitHub compiles without problems now, but a run-time error (access violation) occurs if you insert a new node into, using the context menu (Add Node -> Default Node).

Do you mean when make a  new graph, or after loading an existing one? Because I can't reproduce that. If you connect from an empty pin to an empty space, is a new node created?
Well, on win 11 its work ok, but in win 10 i'm catch it. In the LazNodeEditor.Editor.pas comment out FEditorPopupMenu.OnClose := @OnPopupClose; in constructor, it's an artifact from the past and unnecessary now.

[simone]

I mean, adding a node to the graph shown in the demo. In an empty graph, the same runtime error occurs.