Closed gavinhoward closed 1 year ago
If you exit Chrysalis and restart, what does it show for Layer 0? If you go into the keyboard settings, what do you see for the 'default layer' setting?
On Tue, Feb 14, 2023 at 1:11 AM Gavin D. Howard @.***> wrote:
Describe the bug I used Chrysalis to create this Layout.json https://gavinhoward.com/uploads/Layout.json. As you can see, Layer 0 is a modified Dvorak.
Nevertheless, after saving the configuration, the keyboard still acts like it has Qwerty as Layer 0.
To Reproduce Steps to reproduce the behavior:
- Download the latest Chrysalis release AppImage.
- Make it executable.
- Run it.
- Import this Layout.json https://gavinhoward.com/uploads/Layout.json.
- Save the configuration.
- Check for Qwerty
Expected behavior
I expected Dvorak.
Screenshots
I wasn't able to save a bundle. Chrysalis froze when I tried.
Desktop (please complete the following information):
- OS: Gentoo Linux, up-to-date
- Chrysalis Version: 0.12.0
Additional context
I flashed the latest firmware before saving the configuration.
The other layers seem to work fine.
— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1256, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2DVLGS6S7FUNCM44KLWXND4ZANCNFSM6AAAAAAU3JKSAI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
It shows Dvorak, and the default layer is Layer 0.
Another weird thing is that Layer 1, which is supposed to be my Qwerty layer, switched to showing Dvorak.
I checked the JSON file, and it seems Chrysalis saved it wrong. Or user error (more likely).
Do you have a second computer you can plug the keyboard into? I'd really like to get a debugging bundle and also to see if the QWERTY behavior is replicated on other devices.
On Tue, Feb 14, 2023 at 2:06 PM Gavin D. Howard @.***> wrote:
It shows Dvorak, and the default layer is Layer 0.
Another weird thing is that Layer 1, which is supposed to be my Qwerty layer, switched to showing Dvorak.
— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1256#issuecomment-1430438138, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2GEKUT2XOAK4NPT3QLWXP6XNANCNFSM6AAAAAAU3JKSAI . You are receiving this because you commented.Message ID: @.***>
I do!
It is an Ubuntu 20.04 laptop.
The bundle is chrysalis-debug.zip.
When I compared the two computers, something interesting happened. The six images below are the keymaps on the Gentoo machine.
(Adding an extra paragraph for space between screenshot sets...)
The six below were taken on the Ubuntu machine.
I don't know why they disagree, but the one on the Ubuntu machine matches how the keyboard actually acts, I think.
I don't know what I'm doing wrong, but maybe I can import my JSON layout on the Ubuntu machine and make it work that way until the problem is debugged.
By the way, both sets of screenshots were taken right after plugging in the keyboard and opening Chrysalis.
Is the Chrysalis build you're using on Gentoo downloaded from our Github or from their build?
On Tue, Feb 14, 2023 at 3:28 PM Gavin D. Howard @.***> wrote:
By the way, both sets of screenshots were taken right after plugging in the keyboard and opening Chrysalis.
— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1256#issuecomment-1430527133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2CMADLNXFXSHXS52ULWXQILTANCNFSM6AAAAAAU3JKSAI . You are receiving this because you commented.Message ID: @.***>
Oh. In the settings panel in Chrysalis, what have you set the host keymap to on each OS?
On Tue, Feb 14, 2023 at 3:36 PM Jesse Vincent @.***> wrote:
Is the Chrysalis build you're using on Gentoo downloaded from our Github or from their build?
On Tue, Feb 14, 2023 at 3:28 PM Gavin D. Howard @.***> wrote:
By the way, both sets of screenshots were taken right after plugging in the keyboard and opening Chrysalis.
— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1256#issuecomment-1430527133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2CMADLNXFXSHXS52ULWXQILTANCNFSM6AAAAAAU3JKSAI . You are receiving this because you commented.Message ID: @.***>
The build on both is downloaded from GitHub.
The keymap was different. I was stupid and didn't realize that that was supposed to be the keymap on the computer. PEBKAC as usual. I'm going to redo my layouts with it set the way it's set on the Ubuntu machine. If it works, I'll close this.
As I thought, it was PEBKAC. I apologize.
Describe the bug I used Chrysalis to create this
Layout.json
. As you can see, Layer 0 is a modified Dvorak.Nevertheless, after saving the configuration, the keyboard still acts like it has Qwerty as Layer 0.
To Reproduce Steps to reproduce the behavior:
Layout.json
.Expected behavior
I expected Dvorak.
Screenshots
I wasn't able to save a bundle. Chrysalis froze when I tried.
Desktop (please complete the following information):
Additional context
I flashed the latest firmware before saving the configuration.
The other layers seem to work fine.