Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jaimie Vandenbergh Newsgroups: uk.comp.sys.mac Subject: Re: Mouse Date: 20 Aug 2020 19:13:48 GMT Lines: 41 Message-ID: References: <8a481ea9-52a3-45ca-8ec4-c2ce2ba4ac22n@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=fixed Content-Transfer-Encoding: 8bit X-Trace: individual.net EpogPx6TdFA/EDemQ31C2gdBRJlOaE8V/dXjs3elEtpsdo0tH2 Cancel-Lock: sha1:Je6rds4alrR/F60B+lRnA1fywro= User-Agent: Usenapp/0.80.8/l beta for MacOS Xref: csiph.com uk.comp.sys.mac:146273 On 20 Aug 2020 at 12:26:09 BST, "Elliott Roper" wrote: > On 20 Aug 2020 at 10:51:08 BST, "Jaimie Vandenbergh" > wrote: > >> On 20 Aug 2020 at 09:38:51 BST, "Sak Wathanasin" wrote: >> >>> On Tuesday, August 18, 2020 at 10:48:24 AM UTC+1, Jaimie Vandenbergh wrote: >>>> I'll tag it down as "an actual functional improvement in Big Sur" then. >>> >>> As far as I know, this has always been available. If you have a keyboard >>> where the function keys can double as hardware settings keys, there will be >>> a >>> setting in the keyboard sys prefs where you can toggle the behaviour of the >>> "Fn" or "Function" key. So with the default setting, pressing the function >>> keys on their own sends the hardware settings codes (brightness, volume >>> etc), >>> while holding down "Fn" while pressing the keys sends "F1", "F2" etc. Or >>> you >>> can have it the other way round. >>> >>> If you don't see this option, it's because the keyboard doesn't have h/w >>> settings keys, or has them on separate keys (ie they aren't doubling-up). >> >> Yep. The 'functional improvement' is just that Big Sur successfully shows >> them >> being pressed in the key map! >> >> Cheers - Jaimie > > As does Catalina. Good-oh. Tim and Martin are having the bugs, it seems. Cheers - Jaimie -- To every complex problem there is a solution which is simple, neat and wrong. -- HL Mencken