-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Ready for Review - [MouseJump] move "common" classes into separate project #34333
Ready for Review - [MouseJump] move "common" classes into separate project #34333
Conversation
… the checks # Conflicts: # src/modules/MouseUtils/MouseJump.Common.UnitTests/MouseJump.Common.UnitTests.csproj
# Conflicts: # src/modules/MouseUtils/MouseJump.Common.UnitTests/MouseJump.Common.UnitTests.csproj
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
So it looks like adding I'm not keen on it as a fix as MouseJump.Common only really needs a reference to |
# Conflicts: # PowerToys.sln
I think this PR is ready for review now - the manual and automated tests all work and the build pipeline is green. The only remaining piece of work is to incorporate the new "MouseJump.Common.dll" assembly into the installer. I'm not super-confident about what is required for that - would someone from the core team be able to help? |
Fixed a bunch of merge conflicts - build is working again. |
@jaimecbernardo - just a quick head-up - before this gets merged into main the new MouseJump.Common.dll needs to be added to the installer, which I wasn't confident about doing myself... |
Thanks for the heads up. It should be added automatically, but it might need to be included in signing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mikeclayton , I've given it a try but after building in Visual Studio the MouseJump exe doesn't seem to be created. Can you please try building the PR from a clean state and verifying? I think the changes done to the .csproj might be related to this issue.
Thank you for the contribution, but can you please make the PR testable? 😉 Thank you!
Oh, interesting. I'll take a look tonight (UK time)... |
Looks like I removed these from the MouseJumpUI.csproj and MouseJump.Common.csproj somewhere along the line...
so it was building in the wrong folder. I'll re-add them later... |
@jaimecbernardo - the latest commit appears to put the build output in the right location now when I run it locally. |
I can confirm it's working well now. Thank you :) Going to spin some builds to verify signing and do the final review after. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you for the contribution!
Summary of the Pull Request
This is an attempt to break PR #33486 ([Mouse Jump] - Customisable appearance - borders, margins, colours) down into smaller chunks because it's gotten unmanageable due to its age and number of commits (currently 37 commits / 205 files changed and 25 merge conflicts).
This PR just moves the files in the "MouseJumpUI\Common" folder into a separate *.csproj project so that it can eventually be referenced by the SettingsUI project to draw a sample preview image when style settings are changed. There's no functionality changes in the code, just a move of the existing classes into a separate project (and updating the namespaces), so it'll hopefully be a lot easier to review than #33486, which can eventually be cancelled.
A separate follow-up PR will re-implement the Settings UI changes to close PR #33486 and Issue #27511.
PR Checklist
Detailed Description of the Pull Request / Additional comments
This PR moves all of the code currently held in the MouseJumpUI project under "src\modules\MouseUtils\MouseJumpUI\Common" into a new project "MouseJump.Common". This will allow the project to be referenced from the SettingsUI project in a follow-up PR as part of the work to implement customisable style settings.
Validation Steps Performed
Hotkey and size settings are automatically reloaded when config file is modified manually (e.g. in notepad) while runner and MouseJumpUI.exe are running