-
-
Notifications
You must be signed in to change notification settings - Fork 40.2k
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
Conversation
qmk_firmware/keyboards/wilba_tech/zeal60/keymaps/tusing/Makefile
Outdated
Show resolved
Hide resolved
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.
Updated/cleaned up/fixed a few bugs. Took away all the RGB timeout settings
|
||
//========================================================== CONFIGURABLE DEFAULTS ========================================================== | ||
extern bool g_suspend_state; | ||
extern rgb_config_t rgb_matrix_config; |
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.
This shouldn't be needed. Especially now. There are query options for all of the rgb matrix config.
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.
what doesn't need to be here anymore?
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.
so take out lines 30 and 31?
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.
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.
Thank you for your contribution! |
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.
CHanges have been made
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.
made changes.
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.
#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.
i'll try that.. Trying to rename this caused my git to get all out of
sync... Not sure why
…On Mon, Nov 9, 2020 at 3:41 PM James Young ***@***.***> wrote:
***@***.**** commented on this pull request.
https://github.com/qmk/qmk_firmware/pull/8953/files#r516255393 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.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8953 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUHEKB2IEK42WNGFV6BLGDSPBO2HANCNFSM4MSKC7HQ>
.
|
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 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 |
That should be done.. How do I fix this?
=========================================
ebfulton@iQ:/mnt/c/Users/eli/documents/GitHub/qmk_firmware$ git status
On branch master
Your branch is up to date with 'origin/master'.
You are currently rebasing branch 'master' on '9e07b7cd8'.
(all conflicts fixed: run "git rebase --continue")
===================================================
ebfulton@iQ:/mnt/c/Users/eli/documents/GitHub/qmk_firmware$ git rebase
--continue
Applying: Added changes recommended by fauxpark
No changes - did you forget to use 'git add'?
If there is nothing left to stage, chances are that something else
already introduced the same changes; you might want to skip this patch.
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase
--abort".
…On Tue, Nov 10, 2020 at 12:43 AM James Young ***@***.***> wrote:
***@***.**** requested changes on this pull request.
------------------------------
In keyboards/massdrop/alt/keymaps/pregame/reading.md
<#8953 (comment)>:
> @@ -0,0 +1,36 @@
+# Massdrop Alt Pregame
This file can be completely deleted.
As I explained above, you may either work locally and push:
git rm -- keyboards/massdrop/alt/keymaps/pregame/reading.md
git commit -m "Delete reading.md"
git push
or work remotely
***@***.***/github/managing-files-in-a-repository/deleting-files>
and pull:
[delete the file through GitHub.com, as detailed above]
[open your Git command-line interface, and run:]
git pull
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8953 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUHEKGUGMQESVZF4OVIJHTSPDOI7ANCNFSM4MSKC7HQ>
.
|
I wasn't aware I made any changes on the web side other than marking things
as done and checking viewed checkbox. But yes, things are definitely out of
sync and I'm not sure how to get it back correct.
…On Tue, Nov 10, 2020 at 12:40 AM James Young ***@***.***> wrote:
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
<6b7201f>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8953 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUHEKDIQBEZBWA76R7NC7LSPDN47ANCNFSM4MSKC7HQ>
.
|
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.
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.
Thanks! |
thank you!
…On Wed, Nov 18, 2020 at 5:55 PM James Young ***@***.***> wrote:
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8953 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUHEKHMK4KAKYFXM3DBQCTSQRNGFANCNFSM4MSKC7HQ>
.
|
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
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
Issues Fixed or Closed by This PR
Checklist