🚀 Feature Request: Hide cursor when screenshot is activated to avoid affecting OCR quality

[grantbarrett]

Please confirm the following:

• I have carefully read the README
• I have searched through the issues page and didn't find a similar feature request.(Including issue that has been closed)
• Easydict has been upgraded to the latest version
• I understand and agree to the above, and understand that the project maintainer has limited energy, issues that do not follow the rules may be ignored or closed directly

Feature description

It would be useful to have the option to automatically hide the mouse cursor when doing screenshots, as the optical character recognition sometimes misreads the cursor as a character. It happens that the cursor is often on top of the text I want to OCR and then translate because that is where my attention is focused and when in the flow of my work, I don't necessarily think to move the cursor first and then have to move it, then do the OCR + translate keyboard command a second time. macOS automatically hides the cursor when it does screenshots, as do most screenshot applications. For just one silly example, when I screenshot the text "能自动识" from the EasyDict ReadMe page, and leave the I-beam cursor over the second character, OCR interprets it as "能蘭动识"! Thank you for considering this request. I appreciate the high-quality of this app and the hard work that has gone into it. I use it constantly, every day, as I work with multilingual texts for more languages than I can easily read, and many that are scans with no selectable text, or which have been badly OCRed.

Use case

It will improve the quality of optical character recognition in the cases where the cursor is inadvertently left over the text being screenshotted.

Proposed solution (optional)

I do not know enough about coding to do this.

Are you willing to submit a PR to implement this feature

• I'm willing to submit PR to implement this feature

[github-actions]

Hello grantbarrett, Thank you for your first issue contribution 🎉

[tisfeng]

Thank you for your feedback, we understand the problem now and will consider improving it.

However, since the screenshot feature uses an old third-party library that has some bugs and is not easy to fix, we plan to rewrite it in Swift in the future, which may take a lot of time.

If anyone is familiar with screenshot and Swift, please feel free to submit a PR.