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

Pulled some functionality from the engame keymap for the Drop Ctrl #8953

Merged
merged 48 commits into from
Nov 18, 2020
Merged

Pulled some functionality from the engame keymap for the Drop Ctrl #8953

merged 48 commits into from
Nov 18, 2020

Conversation

elijahblake81
Copy link
Contributor

@elijahblake81 elijahblake81 commented Apr 27, 2020

Description

Added Static
Red Escape
Green WASD/Arrows
Most QMK Animations/Effects are included.
Keys in the 2nd/Function Layer light up if they have a use.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@zvecr zvecr added the keymap label Apr 27, 2020
@elijahblake81 elijahblake81 requested a review from zvecr April 28, 2020 00:19
Copy link
Contributor Author

@elijahblake81 elijahblake81 left a comment

Choose a reason for hiding this comment

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

Updated/cleaned up/fixed a few bugs. Took away all the RGB timeout settings

@elijahblake81 elijahblake81 requested a review from drashna April 30, 2020 16:41

//========================================================== CONFIGURABLE DEFAULTS ==========================================================
extern bool g_suspend_state;
extern rgb_config_t rgb_matrix_config;
Copy link
Member

Choose a reason for hiding this comment

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

This shouldn't be needed. Especially now. There are query options for all of the rgb matrix config.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

what doesn't need to be here anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so take out lines 30 and 31?

Copy link
Member

@drashna drashna Aug 22, 2020

Choose a reason for hiding this comment

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

Both of them have functions to return their values. Which is ... easier to manage, especially if there are architectural changes.

https://docs.qmk.fm/#/feature_rgb_matrix?id=query-current-status

So, yeah. And anything that uses them explicitly would need updating.

@drashna drashna requested a review from a team May 19, 2020 09:58
@stale
Copy link

stale bot commented Jul 3, 2020

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

Copy link
Contributor Author

@elijahblake81 elijahblake81 left a comment

Choose a reason for hiding this comment

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

CHanges have been made

Copy link
Contributor Author

@elijahblake81 elijahblake81 left a comment

Choose a reason for hiding this comment

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

made changes.

Copy link
Member

@noroadsleft noroadsleft left a comment

Choose a reason for hiding this comment

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

#8953 (comment) still needs to be resolved.

You may need to rename twice – e.g. README.md -> read me.md -> readme.md – to get it to take.

@elijahblake81
Copy link
Contributor Author

elijahblake81 commented Nov 10, 2020 via email

@noroadsleft
Copy link
Member

Ah, you seem to be using GitHub's web interface as well as a local cloned repo for your QMK work. This is fine, but managing pull requests can be a bit confusing working this way.

When you push a branch from your computer to GitHub, GitHub actually creates a copy of your local branch on their servers. Your local Git install can and will keep track of the relationship between the branch on your computer and the branch on GitHub, but the two aren't inherently linked – you can make changes to one without modifying the other.

When you change either branch (local or remote), that branch's state diverges from the state of the other branch. Because commits in Git are hierarchical, commits have a parent-child relationship, and the branches themselves exist in sort of parallel universes.

So when you initially push a branch to GitHub, the remote copy of the branch is the same, but if you then use GitHub.com to change that branch, your local version is completely unaware of that change. To make your local copy aware, you need to pull the remote changes to your local branch. Usually a simple git pull is enough to do this. Once both versions have the same state, you can work from whichever version suits you, but when you're done, the other branch needs to be made aware of what has changed. That being the case, you can 1) edit the branch locally, and git push the changes to the remote, or 2) edit the branch on the remote, and git pull the changes to your local repository.

Failure to synchronize the branches before editing one is what creates the situation where you have to merge one branch into the other, as you've done in 6b7201f.

@elijahblake81
Copy link
Contributor Author

elijahblake81 commented Nov 10, 2020 via email

@elijahblake81
Copy link
Contributor Author

elijahblake81 commented Nov 10, 2020 via email

Copy link
Member

@noroadsleft noroadsleft left a comment

Choose a reason for hiding this comment

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

Sorry it took me so long to get back to this; have had an unusually busy week.

Anyway, just some stuff on the readme I noticed. Everything else looks good to me.

keyboards/massdrop/alt/keymaps/pregame/readme.md Outdated Show resolved Hide resolved
keyboards/massdrop/alt/keymaps/pregame/readme.md Outdated Show resolved Hide resolved
@noroadsleft noroadsleft merged commit 6dc2d59 into qmk:master Nov 18, 2020
@noroadsleft
Copy link
Member

Thanks!

@elijahblake81
Copy link
Contributor Author

elijahblake81 commented Nov 19, 2020 via email

xgnxs pushed a commit to xgnxs/qmk_firmware that referenced this pull request Jan 9, 2021
Pulled some functionality from the endgame keymap for the Drop Ctrl.

* very shortened version of the Endgame keymap

* fixed pictures

* fixed link

* fixed link

* fix files

* add GREEN RGB

* fixed GREEN RGB

* not supposed to be in my fork...

* wasn't supposed to be in my fork.

* I have fixed the layer 0 RGB Settings; you can now apply layer using "COLOR" in the layout template.

* I've renamed to pregame, fixed several files

* added Underglow RGB layout, changed def
ault RGB color

* fixed the color of the default profile like i want it

* Added IRL Photo

* Update keymap.c

disabled debugging.

* Update keymap.c

* Update config.h

* Update README.md

* Update keymap.h

* Changed some settings on rules for clean up.

* Changed some settings on rules for clean up.

* fixed some errors, cleaned things up

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Fixed changes recommended by Fauxpark

* Added changes recommended by fauxpark

* trying to fix my repo

* Still trying to fix merge issues

* changed to lowercase

* Delete reading.md

* Trying to rebase my repo

* stuck in rebase loop trying to fix local files and update

* updating readme file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants