Mac: Keyboard Shortcuts Killed by Bug • Hacker News Board

Re: Mac: Keyboard Shortcuts Killed by Bug

#111

Post by Wowfunhappy » Wed, May 15, 2019, 11:06 PM UTC

jacobsenscott wrote: post #34

tyingq wrote: post #29

Earlier quoted context omitted.

Is there some credible source as to what percentage of revenue or profit MacOS drives versus the rest of the org?

I'm sure there are lots. This shows iphone dwarfs all other sources of revenue https://www.apple.com/newsroom/pdfs/Q4-18-Data-Summary.pdf Apple is a phone manufacturer. Computers are a side business.

If spun off into its own business, the Macintosh business would still be a fortune 500 company.

I get that Apple makes more revenue from other products, but the Mac is still extremely profitable. They ought to give it some attention on those grounds, if nothing else.

Re: Mac: Keyboard Shortcuts Killed by Bug

#112

Post by Wowfunhappy » Wed, May 15, 2019, 11:08 PM UTC

diegof79 wrote: post #56

derefr wrote: post #11

> This isn’t a subtle bug which only occurs in certain circumstances. Sure it is. OP is an outlier in how they use this panel. Most people just use it to enable/disable the built-in menu commands, or to modify their accelerators. One very common use-case for people who speak multiple languages is enabling the keyboard switcher accelerator. I expect that they have extensive tests for common use-cases like that. On the…

> The fact that it didn’t get caught during any of the numerous betas since Sierra, really, really implies that nobody ever thought to try this—users or developers. There is another explanation. The author says that he was able to reproduce it always, but I use this feature all the time and I don’t have that problem, so probably there are other factors that cause the bug. You asume that nobody uses this feature, beca…

Did you try it? It takes less than a minute. I found I was one under the number of shortcuts necessary for the bug to appear.

Re: Mac: Keyboard Shortcuts Killed by Bug

#113

Post by Wowfunhappy » Wed, May 15, 2019, 11:11 PM UTC

kccqzy wrote: post #80

wlesieutre wrote: post #15

My complaint about this preferene pane - no wildcards in menu names. macOS has a handy "Batch rename" feature in the contextual menu when you right click on files. The renaming GUI gives you options for sequential numbers, text replacement, prefixes, suffixes, inserting dates. But the menu to open this is called "Rename X Items…" so you can't assign a keyboard shortcut to it. Might be 5 items, might be 2914 items. Wi…

You can make an actual Automator service to do the batch renaming and then call it whatever you want. The Automator version also has more features than the Finder one.

This, but I think the more general point here would be that the system preferences panel is for dead simple stuff, and Apple does provide more powerful tools (namely, Automator and Applescript) if you need them.

I love Applescript. My entire home entertainment setup basically runs on Applescript—each button on my Harmony remote triggers a different script.

There's no equivalent on Windows—you can use Autohotkey, kind of, but without any sort of Apple Event-esque specification it isn't nearly as useful/nice.

Re: Mac: Keyboard Shortcuts Killed by Bug

#114

Post by Wowfunhappy » Wed, May 15, 2019, 11:23 PM UTC

> What is more, as far as I can see, this bug has existed since macOS High Sierra 10.13.4, almost a year ago, in March 2018, if not before.

Hmm, I still have my main machine on High Sierra due to nVidia drivers (and Mojave's Apple Event Sandboxing being a giant PITA), and I can't replicate this on 10.13.6. The bug worked on my Mojave machine, however.

I wonder if the author is mistaken regarding how long the bug has been present. Or maybe it was introduced in 10.13.4, got fixed, and then was broken again?

Re: Mac: Keyboard Shortcuts Killed by Bug

#115

Post by passivepinetree » Thu, May 16, 2019, 12:22 AM UTC

> In coding terms, it’s a trivially simple error which should take a few seconds to fix.

This is both a large assumption and a huge oversimplification. What about time to regression test, QA, deploy through the various inner rings/dogfooding groups, check accessibility, etc.?

It smacks of a writer who possibly has coded before as a hobbyist but never professionally.

Re: Mac: Keyboard Shortcuts Killed by Bug

#116

Post by bla3 » Thu, May 16, 2019, 12:26 AM UTC

ampersandy wrote: post #88

bla3 wrote: post #81

Earlier quoted context omitted.

That bug was fixed in 14 days if I read that page right. The complaint here isn't just that the bug happened, but that it happened long ago, is fairly visible, and is still around a year later.

Because they actually bothered to file a bug report. The author thinks what's obvious to them must be obvious to everyone so didn't file anything. Of course it isn't going to be fixed in a timely fashion.

I have filed a few rdars. It's not a good investment of time in my experience.

Re: Mac: Keyboard Shortcuts Killed by Bug

#117

Post by Bahamut » Thu, May 16, 2019, 5:06 AM UTC

anbop wrote: post #107

favorited wrote: post #92

Earlier quoted context omitted.

> Even if that team is "Craig and his direct reports" or whatever, and even if that team has other responsibilities. And if those "other responsibilities" are iOS, tvOS, and watchOS, then there is no "macOS team." There is the software engineering organization.

I don’t get what you’re trying to express. Is there anyone at Apple who works only on Mac OS? The senior most such person is the de facto boss of Mac OS.

I think you're not grasping the difference of how Apple is structured compared to most companies, and why I made the comment I did, which is completely verifiable.

Apple slices up departments by function, not by product, which is why there are organizations under Tim Cook such as Software Engineering, Hardware Engineering, Internet Services, etc. Everyone and no one is responsible for shipping all the products as a result of this structure. Software Engineering in particular is responsible for all of the operating systems that powers Apple hardware.

Similarly, this is how smaller departments under each SVP/C-level org are subdivided, and so on to the team level. Each team may be responsible for a particular product, which includes all the experiences for that product across operating systems. There is no single engineer responsible for just macOS/iOS/tvOS/watchOS. Everyone is responsible for everything, and similarly no one is responsible for anything.

Apple's structure is unique compared to other companies, and contrary to how most are run, which probably contributes to your confusion.

Re: Mac: Keyboard Shortcuts Killed by Bug

#118

Post by michaelmrose » Thu, May 16, 2019, 5:14 AM UTC

JadeNB wrote: post #91

michaelmrose wrote: post #83

Earlier quoted context omitted.

You began this post with with a sentence fragment and a massive quote from the article everyone just read wherein no particular point required a reference. You used "lol" in written communication which makes you sound like a 12 year old girl texting her friends. You then continued in mid stream and concluded a sentence that you never began. You said "make sure you understand what is a computer" which makes zero sense…

> Your entire communiqe could have been written like do. It's not clear what was gained by your point-by-point rebuttal (of presentation rather than content), but it was worth it for this unproofread line.

That is funny and ironic.

Re: Mac: Keyboard Shortcuts Killed by Bug

#119

Post by fnky » Thu, May 16, 2019, 11:19 AM UTC

ggg2 wrote: post #93

simongr3dal wrote: post #73

Earlier quoted context omitted.

I'm not saying it is easy or logical, but it is possible. System Preferences > Keyboard > Keyboard > Modifier Keys... In this dialogue you can remap what the modifier keys means, so you can make the ctrl-button act as cmd and make the cmd-button act as ctrl. Personally i use it to make the caps-lock key act as escape.

now you have the problem of making your crap accessibility hardware closed source firmware to send the caps lock key code instead of ctrl. Good luck with that.

You can change modifiers for different inputs. If you have another keyboard attached, it will give you the option to choose between that, and other keyboards, such as the built-in. They can have different modifier overrides.