Chrysalis detects the Atreus by its USB Vendor and Product ID. If those remain intact when flashing a QMK firmware onto it (and as far as I remember, they do), Chrysalis will be able to detect the keyboard. However, it will not be able to talk to it, and will guide you to the Firmware Update screen.
It is technically possible to teach QMK to talk the same protocol as Kaleidoscope, and work with Chrysalis just as well as Kaleidoscope does, but there will be certain incompatibilities (ie, keycodes are different between QMK and Kaleidoscope, for pretty much all keys outside of the standard USB keyboard set) that make this impractical at this time.
Thank you both Daniel and Gergely for that information. My intent is to use one or the other exclusively. I did not mean to flash the Atreus with QMK and then try and configure it with Chrysalis.
With my Ergodox + QMK I have programmed some advanced features and not sure of Kaleidoscope could do the same for my Atreus. I was however curious how I would return the Atreus to factory defaults if I ever needed to do that. I believe you answered that for me - I just must not change the Vendor and Product IDs.
Either way, I’ll first continue playing with Kaleidoscope to see what everything it can do.
Talk about this !
Kaleidoscope is open source, and contributions are welcomed, so open a Feature Request or even a PR on the repository and maybe your advanced things can be shared for all the community
A few things off the top of my head, but I’ll have to double check my Ergodox QMK layout to find them all
I can bind Backspace on tap, and Momentary Layer switching on hold, but double tapping and holding the backspace key will trigger repeating backspace, and not switch to the layer.
I can program a single key to be Copy when tapped and Cut when held.
Granted I’ve only had my Atreus for a couple days now, and couldn’t see how to do the above using the default firmware and Chrysalis. I still need to explore the underlying firmware source code. So these things might already be possible with a custom firmware.
This feature hasn’t been merged yet, but there is a PR for it. I’ve tested it, but it will probably get merged sooner if other people try it out and confirm that it works for them (or report problems so I can fix them).
This can already be done using Qukeys. In the keymap, use LCTRL(Key_C) (assuming Linux/Windows), and then define a qukey with an alternate key value of LCTRL(Key_X). Consumer Control keys will also probably work.
[Note: this can’t be done via Chrysalis alone, unfortunately]