Andrew

In your example, you could do: 1.45-.78=*300 As for adding auto parenthesis, it's very difficult to second guess what people would actually want when it comes to opening bracket positioning. In the example given, what's to say that 4+9*8) should be auto completed to (4+9*8).

@dmayo2 Alfred has never done this, however, you can press = during a calculation to equate it to the answer before continuing.

@raguay.customct before killing Alfred, could you please sample the process in Activity Monitor. This hang will be Alfred waiting on something from macOS which is expected instantly, and the sample process may give an indication as to what this is.

I've seen your email on this, and this is the first time this has cropped up. What's interesting here is that Alfred isn't doing anything particularly special / low level for rendering these. For example, the Preferences tab, l am simply overriding the drawRect of an NSView and doing some simple NSBezierPath rendering. Alfred isn't defining or limiting the colour profile in any way. Are you seeing performance issues with other apps? Have you installed any 3rd party drivers or extensions to get your Dell display to "render properly" which could be interfering? Have you tried on a fresh user profile to see if there is any underlying issue on your main profile? Have you reported this issue to Apple, as fundamentally, this is going to be a system wide OS issue? Cheers, Andrew

@luckman212 Thanks for spotting this - I'll get it fixed in the next release

A few things of note here: Alfred runs as a user level process, and doesn't install any lower level OS based extensions, so isn't even capable of creating a kernel panic. This is unless one of the macOS APIs Alfred is using is bugged or corrupted, more likely the latter as this is the first mention of this I've heard. There is no underlying rendering differences between 4.0.5 and 4.0.6, so I'm certain that the behaviour difference is purely coincidental. A few users have seen graphics bugs in Catalina in both the Alfred window and the macOS dropdown and popup menus (where Alfred isn't installed) based around the window blur. If you select the Alfred Classic theme (or create a custom theme and set the window blur to 0), then this will rule out the blur causing a GPU issue. Have you tried running on a new user account to rule out another underlying app (which you may not even know is installed) interfering with your Mac's operation. Kernel panics are unusual, but Catalina is new and notoriously buggy still. If you upgraded via an old OS, or via the macOS Beta path, there may be an underlying OS corruption or misconfiguration. Are there other quirks you are experiencing on your Mac? Cheers, Andrew

@Matt V Could you also set the theme to Alfred Classic. I'm wondering if Alfred is shown on screen, but invisible as per the graphics glitch also reported here.

@luckman212 thanks for reporting this to Apple. I've been playing with it a little more this morning and have gathered a bit more info on the underlying behaviour. Essentially, when a custom view is assigned to a menu item, Catalina is not passing mouse up events for the bottom ~9 pixels of the menu item, even though mouse moved events are still being passed (hence the colour items showing the hovered colour correctly). When I get a moment, I'll create a simple test case app and report a bug to Apple too. I've just done the 4.0.6 release, and have "worked around" this issue by doing two things. Added a separator above the colours (where necessary) so that the "Edit Note..." item is no longer affected by the bug Made the colours slightly larger, and added a 9 pixel inset below the colours which are also ignored in the mouse move, so Alfred treats the Catalina bugged "dead zone" as irrelevant. Let me know how you get on with this workaround. Cheers, Andrew

@JamieKeene I agree with Dean here, Alfred can't EVER know if that drive will exist at startup, which is why you get the warning message showing. I'm going to move this into feature suggestions and change the title, as if it becomes a common problem, it might become something worth investigating.

@luckman212 this looks like a Catalina bug as you also have to click the top half of the normal menu items too, such as the "Edit Note..." item above the colours. I'm not sure there is much I can do to work around this behaviour 😕

@haohailong this will be because of Alfred's caching, my suggestion still holds.

@hzlzh Focusing on trying to fix things in Alfred is the wrong approach, the underlying OS / macOS indexing isn't working. If you are installing Onyx, and enabling root on your Mac, you are past the point where any further suggestions from me will be relevant. Have you been using the macOS Catalina Betas? Or did you upgrade to Catalina? If so, something may have become corrupt during this process, and you may simply benefit from a fresh Catalina install (i.e. format and reinstall, not just install over the top).

@haohailong That's the Catalina equivalent of adding / to your search scope, which we don't recommend. As previously suggested, It would be better to find the *REAL* location of the Setapp apps and add that folder instead. Cheers, Andrew

@hzlzh The metadata tool for Firefox shows that this isn't being indexed by macOS. Until this is the case, Alfred and Spotlight won't be able to find it. It looks like you've followed the recommended steps we suggested. [Moving to Discussion and Help, as the bugs forum is for Alfred bugs]

Have you tried uninstalling and reinstalling the app from Setapp? Or even just manually deleting the app from the Setapp folder and copying back in manually to see if it's found? Correct, and I haven't heard others with the problem too. This isn't a bug in Alfred, it's a macOS indexing issue which is outside of Alfred's control. Catalina is still pretty new and quirky, so it's difficult to identify what's actually happening here.