the-via / keyboards

VIA Keyboards

keyboards's Issues

Greather than (>) and less than (<) key is not supported and it is needed for ISO-ES layout

If i bind it with the 'special'/'<' default VIA mapping, it gives a semicolon symbol, I think that it is intended to correspond to the less-than key ubication in some ISO layouts, but not for the Spanish:

I didn't find any other potentially solution yet.

Keyboard: Discipline65

Issues with qmk_underglow

I thought it'd be better to combine the issues with qmk_underglow in one issue, might help out.

• Color or rather, saturation is preserved in QMK Underglow lighting modes "Swirling rainbow" and "Cycling rainbow", so either a slider or simply allowing change of color in these mods would properly allow configuration.
• Effects have between 1 - 4 speed settings, but the selector always expects 4. I have handled it firmware side, but would be good to tweak client side (see here)
• "Swirling Rainbow" and "Snake" have a reversed direction setting.
• "Static gradient" mode 10 variants... Not particularly important but just pointing out what's there but not configurable through VIA atm.

ISO Layout double pipe key

When ISO enter key and split left shift are selected under layouts, the (# ~) key and pipe key act as the same key.

With this layout pipe key does nothing on press and (# ~) key still works as normal despite not being allocated.

When in key tester pressing either one of these keys causes the pipe key to actuate.

This is on the KBD67MKII Soldered

Does via support SpaceFn ?

QMK:

“Space FN” (tapping = space, holding fn layer)

Thanks

Right shift works when used but in matrix tester it does not

I use this layout on a KPrepurblic XD60 Rev. 3 and everything seems to work, but VIA matrix tester doesn't recognize the right shift:

(sorry for the weird-looking window of the layout, I already commented the existing issue #323 about that display problem)

Iris v6 lighting support

The Keebio Iris Rev. 6 has per-key RGB leds and underglow RGB leds, but I noticed lighting is set to none. Can support for RGB lighting be added?

For what it's worth: when I upload a draft definition that includes a lighting value, I am finally able to add QMK Lighting assignments to the different keys, though the Lighting tab does not work (it becomes a blank screen which requires to restart the application).

Custom modifier key

how do I add a QMK code like GUI_T(KC_ENTER)?

Caps Lock (as input switcher) on MacOS

In VIA, the Caps Lock key locks up every key as uppercase. However, in MacOS the Caps Lock key is also able to switch input sources. There seems to be some conflicts between a locked Caps Lock key and MacOS's function to switch input sources.

https://user-images.githubusercontent.com/78362796/106576558-40a57c00-6578-11eb-9bfe-c76a69efb839.mov
A keystroke on the Caps Lock key of MacBook's built-in keyboard results in an instantly freed Caps Lock key and switched input source.

https://user-images.githubusercontent.com/78362796/106577711-a80ffb80-6579-11eb-853b-cff9428671a3.mov
In the MacOS version of VIA, a single stroke of the Caps Lock locks every key in uppercase while switching the input source, causing the problem.

Not supporting certain backlight values causes a crash

Not sure where you want issues, so I'll open them here for now.

When trying to make some of the RGB code work, I found that not support backlight values 7 and 8 (disable on USB suspend and disable after timeout) causes a crash when entering the Advanced menu in Lighting.

I reproduced this on MxSS with this extension over the PR:

"lighting": {
    "extends": "qmk_underglow",
    "supportedBacklightValues": [
      9,
      10,
      11,
      12,
      14,
      16,
      18,
      20
    ]
  },
Adding 7 and 8 fixed the crash.

Separate out Protocol 10+ vs Legacy json

@Wilba6582 + @ValdisThomann to discuss

How to run VIA locally to test keyboard support

Hello there I'm trying to add support for a new keyboard. I took care of the QMK side, I was wondering how to try it out locally before submitting the PR here. I assume I have to compile and run the electron app locally but I can't find any direction about it. Is it the "reader" project?

Thanks!

Melody96 Matrix Issue

There is a matrix issue for the Melody96 where the backslash and the enter key is swapped. Using the matrix tester, the enter key activates the backslash and vice versa.

This seemed to be an issue with the old QMK firmware before from what I could gather.

kbd67 mkii rgb v3 missing lighting tab

In the GUI the tabs to the left for the KBD67 mkii rgb v3 is missing the lighting tab.

https://github.com/the-via/keyboards/blob/master/src/kbdfans/kbd67mkii/kbd67mkiirgbv3.json
https://github.com/qmk/qmk_firmware/blob/master/keyboards/kbdfans/kbd67/mkiirgb/v3/config.h

Skog Lite - Not showing up in VIA

I flashed the VIA firmware for my Skog Lite and after doing so, it does not show up in the VIA editor.

Right Shift and Right Alt (AltGr) when held (RSA) is not supported

I trying to configure a key using VIA that requires the QMK code RSA, but seem that it doesn't work an is replaced by the "ADV" code.

According to the QMK keycodes modifier keys the RSA modifier is supported:
https://docs.qmk.fm/#/feature_advanced_keycodes

I tested VIA with the RSHFT modifier and it works perfectly but not with the RSA modifier.

Is it possible to use DEVICE_VER to separate VIA JSON by keyboard revision?

Is it possible to use DEVICE_VER to separate VIA JSON by keyboard revision?

Unicode Enable

Is there a way we could have the ability use or enable unicode? I would like the ability to have a built in paragraph key with ease. It's something allowable in the qmk firmware, and since this is an extension I'm thinking it should be possible?

Think6.5 keymap viewer/layout (?) error

Layout shown for the Think6.5 V2 PCB has some keys overlayed on top of other keys, making it difficult to access. It doesn't show the proper placements of keys for ISO layout(ex. iso enter top half in the wrong row, two keys representing one physical key not in the right place). I am not too keen on how to explain the issue or posting it on Github.

Screenshots below show the issue of key overlaps and misplacement and show the issue a lot better than I can explain it.

Why are there only 15 Macro

firstly thank you to all those involved with VIA and bring programmability to those of us too scared to use qmk.

I ordered nk65 milkshake 3 month again, after reading about this new thing call VIA that gives the power of programmability without having to deal with qmk.

I just got my nk65 yesterday and used VIA for the first time and I have to say I am really disappointed with the programmability and functionality of VIA to say the least. It only 4 layers in total and only 15 macro?

I paid $300 AUD for the nk65 as a replacement over my po3ker. Yet it is weaker than my 5 year old board with no real programmability.

There is nothing on your website caniusevia.com that says that VIA has only 4 layer and 15 macro. If you have mentioned that VIA has only 4 layer and 15 macro I would never have bought the nk65. It offers no additional benefit over my pok3r.

VIA should NOT be promoted as a qmk alternative by any KB manufacturers if it has virtually no programmability.

I know VIA has no control over KB manufacturers but on caniusevia.com you should make it clear of the limitations so consumers dont wasted money and time only to find that VIA is no where close to the power of qmk.

flehrad Big Switch firmware on website doesn't have extrakey enabled

How to perform changes to keyboards json definition and apply changes locally

I'm always happily hacking around in my keyboards and recently added RGB to my discipline v2. This is all working well but I am lacking the lightning configuration options in VIA as the default json definition of this keyboard sets lightning to "none". While I am aware how to change the file to support lightning options I cannot figure out how I can make VIA apply these changes. Any hints would be helpful.

Thanks for a great tool.

KBDpad MKII

Flashing a KBDpad MKII with the via firmware allows the keypad to work but causes via to freeze when open, cause via to stall when booting and it never detects the keypad.

Lily58/light - Not detected by Via

Hello,
It seams that the board lily58/light is not detected by VIA.
It seams that the vendor is not in the ‘known list’ of Via.
(Changing the product / vendor id by the ‘rev1’ product / vendor works)
Can you check it please ?
#define VENDOR_ID 0x7983
#define PRODUCT_ID 0x4C4C // "LL"

Some boards are not recognized for me on Via for Mac, but are working fine on Windows

I noticed that using the same Usb-c to A adapter for windows always works. However, the WT75-C (PCB for the 7V) and the WT65-F (Jules) aren't recognized on the same adapter for Mac. I was wondering if all boards were having issues on Mac, but some of my other boards (like the Mode 80) were able to be recognized on my Mac just fine. This is the only USB-C to A adapter I have, so I am unable to check if this is a weird adapter compatibility issue on Mac.

Keycodes shifted by one

Change in qmk/qmk_firmware#9940 causes keycodes after MIDI block in quantum_keycodes.h to shift by 1, which causes VIA to show wrong labels for certain keycodes, like RGB and backlight controls.

Some special keys do not display correctly

Because this bug seems to be holding back #128 I'm making an issue.

The Big Ass Enter and maybe other partial keys do not get placed correctly into the keyboard on the configuration tab of VIA:

See the layout PR for the json file I used

FoxLab Key65 Universal Wrong Key for non split Backspace

Wrong key is set for non split Backspace. Need to split it in layouts to actually change the correct key. The correct key is the first one in the split.
@1ps3

Support for Massdrop CTRL Keyboard

Hello,
I'm very new in QMK world. I want to buy keyboard with VIA support and I'm thinking about Massdrop Ctrl.

I'm wandering if there is possibility to add VIA support to Massdrop CTRL Keyboard?
I downloaded QMK firmware and I saw there is a preprocessor flag "VIA_ENABLE". I have compiled firmware successfully with enabled flag.

There are any technical obstacles to add that support aside from compile QMK with enabled flag and add metadata .json file in VIA?

I can't perform tests because I don't have hardware yet.

Layer issue

When trying to programme the " | \ " KC_BSLS button on a new layer it functions as a hashtag button.

RGB Speed Option

I'm using crkbd with VIA. When I change the RGB effect speed, the speed doesn't change.

Update for m1-Mac

Possible for an update?

Handling rotary encoder keycodes in VIA

Hi, I'm making a keypad with a single rotary encoder and I want to configure the keycodes triggered by CW/CCW rotation from inside VIA.

I saw that the satisfaction75 keyboard did something like this, I looked at the via.c and satisfaction75.c, but mainly my problem is that raw_hid_receive_kb never gets called because I have no idea how to send an unhandled command, so that raw_hid_receive yields to my custom method.
I have seen that the satisfaction75 has some custom menu .tsx files in this repo, and that's probably where the custom command gets sent. What's the correct way to implement some custom components/menus and test them locally?

Or is there a simpler way to achieve this? I tried adding two mock buttons to the keymap, and I can assign keycodes to them in VIA, and I could wire the encoder_update_kb method to read the correct eeprom location and get their keycodes, but I haven't found a way to do that.

scr- doesn't work

os:manjaro linux
maybe the KDE causes the problem, but scr+ works well.

os:window 10 everything is fine.

"Any" under special key overwriting while entering

When trying to enter a custom keycode using the Any key under "special" it actively overwrites keys on the keyboard in the background.

New board layouts are crashing the GUI

As per main thread issue #115(the-via/releases#115), and #153 (the-via/releases#153). As this issue has been present for quite a long time I was wondering when there might be a resolution to this?

What can I do if my keyboard isn't supported?

I have an XD87HS and it isn't supported yet. Is support planned?

I'd love to contribute but unfortunately I'm no good at programming :(

Please add durgod hades

Please add support for DURGOD Hades!
There is already support for durgod taurus.

Mouse keys not mapped correctly

There is an issue when setting mouse keys in VIA.

For example, setting KC_MS_UP on a key makes it do nothing.
However, putting in its hex-code 0xF0 makes the mouse key work. Is this mapped incorrectly within VIA, or does it lack the necessary definitions?

Maartenwut Wonderland Wrong Key for Backspace

The wrong key is set for non split backspace.
It's the second key not the first for non split backspace.

You have to split the backspace in layouts, then change the key for it to change correctly.

Support Tap-Hold Configuration options

Hello,

Would it be possible to support custom values for Tap-Hold Options in VIA?

It would be great to have support for the global options at least:

• TAPPING_TERM xxx
• PERMISSIVE_HOLD
• IGNORE_MOD_TAP_INTERRUPT
• TAPPING_FORCE_HOLD
• RETRO_TAPPING

and out of those the first three would be of great help for fast typists.

Read Layout QMK Firmware side?

aside from reading the eeprom constantly, is there a good way to read the current layout options?

Would like to enable/disable LEDs in the rgb matrix based on the status of the layouts, but there doesn't look to be a way to do so?

HID Interface for lighting control.

Is there an existing interface for VIA firmware that would allow lighting override via HID? What would be great is an interface, key-by-key (or zone by zone if that's the hardware implementation), starting at the top left controllable element and moving in a grid pattern to the right->down.

I'd be more than happy to help with this impl - I'm not sure this is the repo for this.

Full ansi, per-key:

[ 0,  1,  2,  3,  4,  5,  6, .., 15]
[16, 17, 18, 19, 20, 21, 22, .., 36]
[...]

sir,can you help me?my keyboard can`t see in the via desktop program

@Wilba6582 ,Sir my Program have merged into the QMK already,qmk/qmk_firmware#8766,can you merge my PR into VIA.thanks a lot again. I see that the via update 1.3.0 by @olivia,but this time i open it ,my keyboard can`t find in the via DESKTOP PROGRAM, and strangely the via official have my latinpad_via.hex in the List.so i think may be some thing wrong? can you help me?
"name": "latinpad",
"vendorId": "0x6C63",
"productId": "0x6C70",

Enter Any QMK Keycode broken

When trying to use the ANY QMK Keycode it just assigns keys in the background with whatever your typing. Example (KC_NUBS) it will just assign the keys in the background starting from K then assign the next with c and so on

Drop CTRL Support?

I saw that the Drop ALT is supported would it be possible to add the Drop CTRL?

Ctrl when held, Esc when tapped?

Similar to the KC_LSPO mapping, is it possible to map a key to Ctrl when held, and Esc when tapped?

VIA not saving design from local JSON file

I've added support for my keyboard in QMK and made JSON file for VIA. After loading custom JSON from design tab everything is working. But after closing VIA does not recognize the board, and i need to load custom JSON again.

Please Support QMK LT() and LM()

Ctrl Shift Esc to launch Task Manager does not work with {Esc`} on esc

I'm not sure how major this is but I did not ice t he behavior and figured I'd report it.

Ctrl Shift Esc to launch Task Manager does not work with {Esc`} on esc key

VIA is not detecting keyboard

I've added keyboard (YMD 75) ) to VIA, but GUI app is not detecting it. If i'm loading json file from PR through design tab, then keyboard is detected.

I've tried to reflash keyboard with firmware from caniusevia.com, but no luck.