Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some usage issues. #424

Open
timpc0526 opened this issue May 15, 2024 · 0 comments
Open

Some usage issues. #424

timpc0526 opened this issue May 15, 2024 · 0 comments

Comments

@timpc0526
Copy link

timpc0526 commented May 15, 2024

Hello,
I'm working within a project environment consisting of VS2022, Qt5.15.2, and Win10. I have several questions regarding the project:

  1. When compiling the .dll files, both the release and debug versions are named QtNodes.dll. Is there a method to distinguish between them, perhaps as QtNodes.dll for release and QtNodesd.dll for debug?
  2. In debug mode, executing the simple_graph_model example in my project results in an error at LINE:996 debug_heap.cpp. This error doesn't occur in release mode. Specifically, the error appears at the end of the traverseGraphAndPopulateGraphicsObjects function in BasicGraphicsScene.
  3. What are the distinctions between using NodeDelegateModel and AbstractGraphModel to create a Node? Additionally, the scenes used, DataFlowGraphicsScene for NodeDelegateModel and BasicGraphicsScene for AbstractGraphModel, differ. They are implemented differently across various examples.

In accordance with the project's requirements:

  1. We need to utilize external buttons to add Nodes, with the option to also use a built-in menu for this purpose.
  2. Each added Node requires a user-defined unique ID.
  3. The input interface should support multiple types of input.
  4. Is there a recommended approach to generate data representing the current connection status?

I look forward to your response. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant