Milly Guitron

So I looked over PlugaruT's work and changed to using a menu button instead of a popover here: 4c32ffc68cfc6421b572615ef6c74f1a2d9d9469 However, I still need to figure out why the text appears...

Is there a way to have MenuItems use their default style context? Or is this the downside of using MenuButton?

It looked like Dan was doing some work on adding a delay-spin to this pretty recently, so I'm not too sure if this change is still needed? Nonetheless, the style...

Would this go in the `quantum/template/base/keymaps/default/keymap.c` template? Or in the `DEFAULT_KEYMAP_C` in `keymap.py`? I see where `__CUSTOM_KEYCODES_HERE__` would be used in `keymap.py`. I think we would be adding a `keymap_c.replace('__CUSTOM_KEYCODES_HERE__',...

So just placing an enum in the default template? https://github.com/jorgemanzo/qmk_firmware/commit/3b451a17617cd22d835b2d7329faca09c8e94e7a Are there any keymap.c files in the repo that define custom keycodes? I have a fair idea of how layers...

I think (might be wrong here) a good place to start would be to look in `lib/python/qmk/keymap.py`. At the top there should be a `__KEYMAP_GOES_HERE__` marker. This whole python string...

After some investigating (and I could be completely off the deep end with this), `Granite.Widgets.SourceList` has a `Tree` class that has a method called `set_selected()` which then calls `Gtk.TreeSelection`'s `unselect_all()`....

So I looked over PlugaruT's work and changed to using a menu button instead of a popover here: 4c32ffc68cfc6421b572615ef6c74f1a2d9d9469 However, I still need to figure out why the text appears...

Is there a way to have MenuItems use their default style context? Or is this the downside of using MenuButton?

It looked like Dan was doing some work on adding a delay-spin to this pretty recently, so I'm not too sure if this change is still needed? Nonetheless, the style...