@MJ1, might I ask what QMK, Via, and Vial are? I’ve never heard of any of this stuff. I assume they’re protocols by which a GUI configures something about the keyboard, like its layout?
QMK is the open source firmware that runs on the Framework keyboards.
Via is the GUI point-and-click interface that you see when you configure your keyboards using keyboard.frame.work. Via is separate from the QMK firmware on the keyboards, and was made by a different group. QMK just includes what is needed to talk to Via (if you enable it, as FW has done).
Vial is an alternative GUI which offers more features and offline desktop apps, in addition to a web browser GUI. But to use Vial to its full extent, you need to put a version of QMK on your keyboards that’s made to talk to Vial instead of Via.
This is what Vial looks like for configuring a FWL16 ansi/american keyboard layout.
Click for pics of other tabs, QMK features that Via is unable to control. + The Macropad
There are more QMK settings. You can see the sub-tabs for those pages. But you probably get the idea. It has more options than Via. Some that one may be interested in, others, like very fine QMK settings, that many probably don’t need to bother with.
There is also a mousekeys settings tab too, if enabled. You can see that on the macropad below. Looks like when he built the firmware he forgot to enable mousekeys for the ansi keyboard. Framework forgot that too! So the stock firmware that all the keyboards come with from Framework doesn’t currently offer mousekeys. It can be enabled, it takes one line MOUSEKEY_ENABLE = yes in rules.mk in the firmware.
This is all Vial 0.7.1. Current as of now. When a newer major version comes out, you can see features added here get.vial.today/changelog
If you don’t have a Framework 16, I’d be happy to post screenshots of Via for any of the keyboards for comparison.
Each of the keyboards, full, numpad, macropad, use their own RP2040 MCU ( microcontroller unit), on which Framework has placed or “flashed” QMK. The RP2040 was a good choice because it’s well-supported by QMK, very easy to flash, and generally hard to “brick” or put into a state where it no longer works.
1 Like
Every time I find my cat napping on my laptop I find the breathing mode enabled. What is it for exactly? Struggling to find any situation where it might be useful.
1 Like
No clue, to be honest.
I’d argue it has no use, besides being a novelty.
But people do like some things that have no practical use. They can bring entertainment and joy to an otherwise boring day. Like RGB lights, for example. Unless you have programmed your RGB keyboard to provide something useful, indication of something, it has no purpose or practical use. But try to deny some people their RGB & you may come out bloody. 
Breathing mode though, how much entertainment can it bring? And it actively distracts, and at night, hinders seeing the keys. Surely the novelty will wear off fast. I do not understand why Framework put Breathing-mode on the default keymap. I seriously suspect it wasn’t fully thought out. One, because it isn’t on their hotkey list, hotkeys-on-the-framework-laptop-16. Two, because people accidentally triggering it leads to confusion for some, questions if their keyboard is malfunctioning, and I imagine at least a few contacting support, costing Framework actual money. Way more hassle than it’s worth having it on the default layout. Of course, if that’s the worse accident one makes, in work as complicated as bringing us the FWL16 keyboards, you can count yourself as extremely lucky.
By the way, you can go to keyboard.frame.work and remove it.
i found one use: sometimes it distracts my cat from wanting to swat at my mouse cursor, because they keep getting distracted by the numpad cycling.
2 Likes