-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New package: Microsoft.Ctrl2Cap version 2.0 #171173
Conversation
Signed-off-by: Dragon1573 <49941141+Dragon1573@users.noreply.github.com>
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Note This package requires manual (un)installation, since Use |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @Dragon1573, Since this is a Sysinternals (MS sub-brand or similar) product, should it be under their |
Maybe it is? 😕 I can't sure if Windows 10/11 is "high enough" or "too high" for Ctrl2Cap.
|
@wingetbot run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Behavior in #171173 (comment) successfully reproduced in Windows 11 Give up and close this without being merged. 😞 |
Checklist for Pull Requests
Manifests
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the directory's name containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow