Bruce D'Arcus

> I'm not sure what version it's in ... It's in the 1.1 branch. > and I'm not sure whether this change is supposed to go along with no longer...

I don't recall why we added custom to 1.1 and not 1.0. Would adding to 1.0 help?

> I don't think there's a problem adding it to 1.0 Let's do it then?

No; I just created a linked issue to make sure we don't cause any problems if we do. I can't imagine we do, but just in case.

I haven't checked, but am pretty sure we're silent on that question ATM.

> ... this seems like something that should have a solution at the style level? Yeah, I can see that. I just don't recall it coming up. Thoughts on this...

I don't really know. But logically, I don't see why one wouldn't. Copying @fbennett @bwiernik @adam3smith

Could you update the docs to reflect the fact that this works for more than just the autoset? Perhaps a FAQ entry with whatever current understanding and caveats are?

> What firmware do you have ? -0401. > Have you tried compiling/re-flashing with the "all_menu" function enabled ? No, in part because I wasn't clear what the purpose of...

It's now confirmed across different machines and fw, including the default autoset and -0401. I assume this is straightforward to fix, but I don't understand how myself.