![]() ![]() I’m generally more fond of my Mac since it just runs more smoother and longer on a battery than my windows machine and having a near alike version of KiCad on the Mac would really be having the cake and eating it too! I’m also very curious to know what others experience has been like using KiCad on the Mac. Since I’m so used to the Windows version now, I find several things that are missing in the Mac version (like the completely different main menus for pcbnew and lack of several setup features) and I wanted to know if I’m missing something in accessing these or they are just not there. Even the most recent nightly was a letdown.Īt the outset let me say that KiCad on Windows is exemplary and all the people who made this possible have my heartfelt thanks! I’ve been using it for more than 5 years and all my boards, prototype and production alike, are made with KiCad. I personally find KiCad on the Mac very unusable and after several attempts (some out of desperation when my Windows machine crashed) I finally gave up and stuck to using KiCad on Windows. All seems good now.This post comes about as part of a discussion started on a Reddit thread and it was suggested that I come here and check if other Mac users are facing similar issues in using KiCad on the Mac. Spotlight reliably starts on first press of cmd-space and I've since disabled that and assigned Alfred the key. It also seems to be advised to run EtreCheck and fix any problems it identifies. The suggested solution was to reboot in Safe Mode (hold down Shift while rebooting) and then reboot as normal. Others have encountered the same issue with High Sierra (in their cases with Spotlight not activating): Looks like I'll be switching to alt-space and will retrain my fingers. ![]() It's much infrequent now but I still occasionally get the problem. UPDATE: I spoke to soon, my problem is back. I'm really getting to despise Apple, but what's the alternative?Įdited to "installing _macOS_ upgrades" to make it clear that it's a rant about Apple and not Alfred :)įIX: On the Apple discussion thread, a number of users have reported that disabling Siri solved the problem of the first activation of Spotlight being ignored ( ) The wealthiest company in the world should allow its users to report bugs free of charge and receive updates on fixes. And I can't raise Apple support tickets like a responsible user to report any of the bugs in *their* software because I'm not under warranty. it just went on and on and on and I still haven't solved my problem! I'm boiling mad and have lost 2 hours to achieve nothing at all. I've just spent 2 hours chasing a crazy bug where I can't activate Find My Mac because it's reporting a Server not responding error and it's led me in a fruitless chase of needing to update my iCloud details, but I couldn't do that because I was in the wrong country, then I couldn't update the country because my credit card is out of date and then the changes wouldn't stick and would just revert on refresh, then the changes activated some potential fraud detection and I got locked out and had to go through a verification loop. It's crazy how a company like Apple, literally the wealthiest in the world, can't sort out basic problems. So I take the upgrades when they are suggested, but I pay the price in all the new bugs and problems. there's no way of knowing (or it might introduce them!). ![]() Particularly if people are adhering to responsible disclosure, your High Sierra upgrade might be protecting you from serious security flaws in Sierra. You don't know what serious bugs are being fixed. I can understand the reasoning of wanting to delay installing macOS upgrades but the passwordless root access highlights the importance of installing patches and updates as soon as they are available. The major difference between my iMac and laptop is I upgraded to 10.13.1 on my iMac where I still run 10.12 on my laptop. I've tried using the second ⌘ key just in case the left key was a problem but I also see the same issue. I worried that the problem was physically with my key but I can trigger Spotlight reliably with ⌃SPACE before I try Alfred which fails, and SPACE never fails when I'm writing normally. I sync my Alfred settings via Dropbox to my laptop, which DOESN'T ever show this problem. I fixed it by rebooting for a while then it returned. BUT if I start working on something and don't trigger Alfred for an amount of time (I haven't determined exactly how long, but it seems to be more than 5 minutes or so), then the first trigger fail happens again. If I hit the hotkey a second time then it activates fine then I dismiss Alfred, and I can trigger it reliably again. On my iMac (magic keyboard2) I have my Alfred hotkey set to ⌘SPACE and if I do not use Alfred for 5-10minutes or more when I press the hotkey Alfred does NOT trigger. ![]() I have a clear issue on one machine, whose reproducibility depends on *not* using Alfred for a while. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |