win-capture: Add Hearthstone Deck Tracker to compatibility list

[beheh]

Description

This PR updates the compatibility file to show a warning when the game overlay window of Hearthstone Deck Tracker is captured via a non-functional capture method (BitBlt or Game Capture):

Correct Capture Method	BitBlt Warning (auto-selected)	Game Capture Warning

I've kept with the style of the other applications in this file. One thing to call out maybe is that this targets the executable and the window name (which we're willing to keep stable). This is because some streamers might still be capturing the chroma window, which works fine with the old capture method. We'll deprecate that in Hearthstone Deck Tracker in future.

I also bumped the version in win-capture/data/package.json akin to past PRs such as #12218 and #12327.

Motivation and Context

My team develops "Hearthstone Deck Tracker", a companion app for Blizzard's Hearthstone that's used by Hearthstone players all around the world. It works by overlaying an invisible window with alpha on top of the game to add some helpful information for the player. Streamers use it to give themselves and their viewers extra context.

In the past, we've asked streamers to use either screen capture or a chroma-keyed window we built. However, we've recently made a change to our app to make the overlay visible to other apps and discovered we can just use the Windows 10 capture method in OBS to make the overlay capturable itself, obsoleting our Chroma key setup (and Screen capture is disliked by somne streamers).

However, to make setting this up easy, we need to ensure the modern capture method is selected so the alpha channel works. In this PR I've updated the compatibility file to show warnings, akin to many other apps. I understand that technically we could also make the "auto" method smarter, however it looks like that mostly works on the framework level right now rather than on a per-app level. As we use a WPF app here, we also only really control the window title, not the window class.

How Has This Been Tested?

I've tested this on my local device, screenshots above.

Types of changes

• Tweak (non-breaking change to improve existing functionality)

Checklist:

• I have read the contributing document.
• My code has been run through clang-format. (noop)
• My code follows the project's style guidelines
• My code is not on the master branch.
• My code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation. (noop)

[Fenrirthviti]

You will need to review and complete the PR checklist before this can be looked at.

[beheh]

Sure, I just didn't check the ones that I didn't think applied to this change as it's JSON-only, mirroring previous PRs to this file. I've re-checked them all and checked the appropriate ones now:

• Style is according ot the docs
• Clang format isn't appropriate on JSON files (seeing a whole bunch of nonsensical violations)
• I don't see a documentation change that would be appropriate (as this is a static config file)

Happy for any feedback otherwise.

[Fenrirthviti]

Thanks, for future reference, this is pulled from our contribution guidelines:

Appropriate templates are presented to the user when opening a new issue report or pull request on GitHub which are required to be fully filled out to be taken into consideration by the project. The template might require checking off items that might not be applicable e.g., the requirement to have the code properly formatted does not apply when the contribution has not changed any source code. It is permissible and preferred to tick the box regardless.

[Fenrirthviti]

seems fine to me at a glance

[beheh]

Ah, thanks for the pointer, that clarifies things!