fix: Update include paths for libimagevisualresult based on QT version

[dengzhongyuan365-dev]

• Adjusted the include statements for libimagevisualresult to conditionally include the correct header file based on the QT version.
• This change ensures compatibility with QT 6.0.0 and above by including libimagevisualresult6/visualresult.h, while maintaining support for earlier versions.

Summary by Sourcery

Bug Fixes:

• Update include paths for libimagevisualresult to ensure compatibility with QT 6.0.0 and above.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the include paths for libimagevisualresult to ensure compatibility with QT 6.0.0 and above. It uses a preprocessor directive to conditionally include the correct header file based on the QT version.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Conditionally include the correct header file based on the QT version.	Added a preprocessor directive to check the QT version. Included 'libimagevisualresult6/visualresult.h' when the QT version is 6.0.0 or higher. Included 'libimagevisualresult/visualresult.h' for older QT versions.	src/main.cpp src/src/filterpreviewbutton.cpp src/src/majorimageprocessingthread.cpp

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @dengzhongyuan365-dev - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider defining a macro to avoid repeating the conditional include in multiple files.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[deepin-ci-robot]

deepin pr auto review

代码审查意见：

1. 版本号更新：

   • 在多个文件中更新了版本号，这是一个好的做法，确保了版本控制的准确性。但是，需要确保所有相关的文档和配置文件都已经更新，以反映最新的版本号。

2. 条件编译：

   • 在src/main.cpp、src/src/filterpreviewbutton.cpp和src/src/majorimageprocessingthread.cpp文件中，使用了条件编译来包含不同的库版本。这是一个好的做法，可以确保在不同版本的Qt下使用正确的库文件。但是，需要确保这些库文件确实存在，并且在所有目标平台上都是可用的。

3. 文件权限：

   • 在loong64/linglong.yaml文件中，文件权限被设置为100755，这通常表示文件是可执行的。如果这个文件不需要执行权限，应该将其权限设置为100644。

4. 代码风格：

   • 在src/main.cpp、src/src/filterpreviewbutton.cpp和src/src/majorimageprocessingthread.cpp文件中，条件编译的#if和#else语句后面应该有一个空行，以提高代码的可读性。

5. 注释：

   • 在src/main.cpp、src/src/filterpreviewbutton.cpp和src/src/majorimageprocessingthread.cpp文件中，条件编译的部分缺少注释说明为什么需要根据Qt版本选择不同的库文件。添加适当的注释可以提高代码的可维护性。

6. 依赖管理：

   • 确保所有新增的库文件libimagevisualresult6/visualresult.h在项目中是正确引用的，并且这些库文件已经包含在项目的依赖管理中。

7. 测试：

   • 在更新版本号和库文件之后，应该进行全面的测试，以确保这些更改不会引入任何新的问题。

总结：

• 版本号更新是正确的，但需要确保所有相关文件都已更新。
• 条件编译的使用是合理的，但需要确保库文件的存在和可用性。
• 文件权限和代码风格需要根据实际情况进行调整。
• 注释的添加可以提高代码的可读性和可维护性。
• 依赖管理和测试是确保代码质量的重要步骤，应该被重视。

[github-actions]

TAG Bot

TAG: 6.5.18
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dengzhongyuan365-dev, lzwind

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment