New Keyboard: Quadrant by Ealdin

[nuno99costa]

Description

Quadrant by Ealdin. This is my first pull request. Hopefully I did it right.

Original Github Repo for this keyboard
Code written by @Ealdin and tested by me. Includes:

• VIA Support
• Default layout

Types of Changes

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

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• 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).

[nuno99costa]

Fixed error with the encoder support on the board (seemed to be based on a previous release of QMK), tested both the default and VIA keymaps and both seem to work now.

[nuno99costa]

Thanks @drashna for the suggestions I will apply them and test on my board and report back if it works well!

[nuno99costa]

Finished testing, VIA and default keymap works. Ended up having to fix a couple brackets and layout names. Thanks once again for the help @drashna !

[nuno99costa]

The changes suggested by @drashna ended up breaking the default keymap. I talked with the pcb designer for this and found out the matrix layout is inverted. As such, the layout mapping in quadrant.h has to be altered and "non standard" to support this keyboard.

Shoutout to @Ealdin for helping me fix these issues.

[drashna]

Using the LED_CAPS_LOCK_PIN definition doesn't work, for some reason, with this board. After testing, I updated the code to use one of the other methods defined in the qmk documentation (led_update_kb function).

You may need #define LED_PIN_ON_STATE 0 as well.

[nuno99costa]

Using the LED_CAPS_LOCK_PIN definition doesn't work, for some reason, with this board. After testing, I updated the code to use one of the other methods defined in the qmk documentation (led_update_kb function).

You may need #define LED_PIN_ON_STATE 0 as well.

I will try this and will update if it works that way. (I would also prefer these simple definitions instead of the "bulkier" functions).

[nuno99costa]

The #define LED_PIN_ON_STATE 0 didn't work out. The current code is using a current suggested implementation and as such is in accordance with QMK guidelines. As such , I believe we can go ahead with the pull request.

[nuno99costa]

Updates from @fauxpark added

[nuno99costa]

Can't understand the issues on the travis-ci build (seems to be trying to build a community layout)

[drashna]

That's fine. Community layouts sometimes error out.