-
Notifications
You must be signed in to change notification settings - Fork 230
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
NuGet package needs to be updated #28
Comments
commenting for added visiblity |
@dantman - I'm working on a major rewrite of InputSimulator. I expect to have it online and available later this week. Once I do, I'd love to get your thoughts on it. |
@TonyValenti How's the status of that? I'd be most interested to test an up-to-date input simulator version. The current nuget just doesn't work for me, at least mouse seems broken on high DPI. |
It works excellent! Take a look: If something isn't happening right with HighDPI, record a video (Camtasia is great) and post the details and repo steps on my github page and I'll dig in. |
Bumping, and also sent a message via NuGet. Codeplex is dead, so the links to project website and license info don't lead anywhere. The project not being maintained is fine, but I'd appreciate it if the links were updated to point to this github. |
It appears the NuGet package has not been updated in a long time.
The README still provides installation instructions despite the package being out of date.
This means the NuGet package is still stuck at an old version still under Ms-Pl and without any scanCode support.
Speaking of the license and NuGet package, WindowsInput/WindowsInput.nuspec needs to be updated with:
Personally I hope #27 is fixed and a new NuGet package is released with it so I can switch back to InputSimulator from InputSimulatorPlus.
The text was updated successfully, but these errors were encountered: