Skip to content
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

use focus and snap hardware buttons #66

Merged
merged 1 commit into from
Oct 2, 2019
Merged

Conversation

jgibbon
Copy link
Collaborator

@jgibbon jgibbon commented Sep 24, 2019

Replacement for #57 with the much better solution you basically provided yourself.

cheers!

@jgibbon
Copy link
Collaborator Author

jgibbon commented Sep 26, 2019

FYI, just rebased on the white space changes in the fix-manual branch.

edit: this whole upstream rebasing/force pushing for the sake of fewer visible commits makes me a bit uncomfortable, but as a guest here I'll just abide by the rules. ;)

@jgibbon
Copy link
Collaborator Author

jgibbon commented Sep 27, 2019

Some more Info to simplify testing:

cheers!

@llelectronics
Copy link
Collaborator

llelectronics commented Sep 27, 2019

Works for me.
Great work

@@ -555,6 +538,35 @@ Page {
}
}

Keys.onPressed: {
if(event.isAutoRepeat) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistent style add space between if and (

@mlehtima
Copy link
Collaborator

mlehtima commented Oct 1, 2019

Maybe also add [some_tag] to beginning of commit message, check the commit history for examples.

@jgibbon jgibbon force-pushed the shutter-buttons branch 2 times, most recently from 1cf8815 to 64cbdfb Compare October 2, 2019 06:33
@jgibbon jgibbon changed the base branch from fix-manual to master October 2, 2019 06:36
@jgibbon
Copy link
Collaborator Author

jgibbon commented Oct 2, 2019

Changes:

  • proposed white space added
  • removed "auto format" white space
  • commit message altered to include [buttons] tag

I checked in with @piggz – I'll make the "===" changes as a different PR to get to test that without hurry and still getting a new release ready soon. I'll create an issue to remember.

cheers!

@piggz piggz merged commit 55ccaac into piggz:master Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants