Skip to content

Enable FsTouchDrawCenter in build process and update source files#47

Merged
Hashory merged 1 commit intomainfrom
touch-draw-center
Aug 23, 2025
Merged

Enable FsTouchDrawCenter in build process and update source files#47
Hashory merged 1 commit intomainfrom
touch-draw-center

Conversation

@Hashory
Copy link
Copy Markdown
Owner

@Hashory Hashory commented Aug 23, 2025

Update the CMakeLists.txt to include additional source files for the FsTouchDrawCenter effect and enable its inclusion in the build process. Adjustments to the TouchDrawCenter.cpp file ensure proper header inclusion.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @Hashory, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the FsTouchDrawCenter effect into the project's build system. It activates the compilation of this effect by updating the main build configuration and incorporating necessary source files, while also refining header inclusions within its core C++ file to ensure correct compilation.

Highlights

  • Enabling Build Process: The FsTouchDrawCenter effect is now enabled in the build process by uncommenting its subdirectory inclusion in prev-build-process.cmake, allowing it to be compiled with the rest of the project.
  • Source File Inclusion: Several new source files, including alphaBlur8.cpp, alphaBlur16.cpp, alphaBlur32.cpp, and copyImage.cpp, have been added to the FsTouchDrawCenter project's CMakeLists.txt, ensuring all required components for the effect are included in the build.
  • Header Reordering: The #include "Fs_Entry.h" directive in TouchDrawCenter.cpp has been moved from the top of the file to the bottom, likely to resolve compilation or linking issues related to header dependencies and ensure proper order of inclusion.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly enables the FsTouchDrawCenter effect in the build process by adding its source files to CMakeLists.txt, updating the main build file, and fixing an include order issue in TouchDrawCenter.cpp. The changes are logical and necessary for the feature to be included. I've added one comment regarding a consistent typo in several filenames. Additionally, while reviewing the newly included source files, I noticed a significant amount of code duplication across the ToutchDraw*, alphaBlur*, and copyImage files. I highly recommend creating a follow-up task to refactor this code, possibly using C++ templates, to improve maintainability and reduce redundancy.

Comment thread Source/Effects/FsTouchDrawCenter/CMakeLists.txt
@Hashory Hashory merged commit 2d2fdd0 into main Aug 23, 2025
2 checks passed
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

Successfully merging this pull request may close these issues.

1 participant