Jump to content

Uupis

Member
  • Posts

    3
  • Joined

  • Last visited

Uupis's Achievements

Helping Hand

Helping Hand (3/5)

0

Reputation

  1. Set the mode, restarted Alfred – no improvement. File still gets copied, but no Universal Actions panel. Thanks anyway!
  2. Sort of, maybe. I want the Universal Action list to appear for the Quick Looked file, and as I understand the Copy event itself is a means to get the current selection. It's a bit odd, because the menu bar remains that of the Finder, so it seems that Finder does get the Copy event, and the file does get copied. The Universal Action panel does not pop up, though. Fair enough. Thank you for the confirmation that it's probably not just a configuration error on my part!
  3. 'elloes! It seems that as of Monterey, if I have the Quick Look window 'focused', pressing my Universal Action selection hotkey activates ⌘C instead. It used to work correctly on Big Sur. Specific steps for the issue I run into: select something in Finder press Space Bar (Quick Look shows up; issue occurs with ⌘Y as well) press the Universal Action selection hotkey → Finder selection gets copied to clipboard (Edit menu highlights, and if it's open – the Copy action highlights) Things I've tried/checked: if while the Quick Look window is open I click on the file in Finder, it works as expected – the file is actioned changing the selection hotkey – doesn't change the wonky behavior, the same issue occurs regardless on what shortcut I've set removing and re-adding Alfred in the permissions preferences (restarted Alfred) – no change close any other apps that might conflict checked the macOS keyboard shortcuts for anything that might conflict, and found nothing I don't have set any keyboard shortcuts in my workflows While searching around on the matter, I've seen it mentioned that Alfred sends ⌘C to get the current selection, which lines up with the bit where the issue occurs regardless of the keyboard shortcut I set for Universal Action selection. Is there anything else I can do to attempt to get to the bottom of this? I can imagine that this is a macOS issue, especially with it appearing after the upgrade, but I would appreciate a confirmation if that's the case. And a workaround would be a wonderful bonus. 😅
×
×
  • Create New...