arhoads76

cool

When in Parallels, if I use a hotkey like Command+Number to run a workflow that activates another app, it does activate the other app but also results in activating the Start Screen (in windows 8, or the Start Menu in Windows 7).

Certainly this is an interaction between two programs.  It might be a problem in Parallels versus Alfred v2, however it did behave differently in v1.  (I've checked, and I don't have a conflicting Workflow mapped in this case.  ;-)

That will be awesome.  Can't say enough good things about your app in general, but especially your help and patience with me.  Thank-you!

I closed all of my programs.  Turned off access for assistive devices.  Double-checked all of the hotkeys.  Couldn't find any conflicts and the trouble persisted.  I went back through my workflows in Alfred v2 and found one that I thought was bound to a different hotkey was in fact using Command+Shift+Space.  I bound that to the hotkey I expected for it, and my problem went away.

My playing with the new workflows caused my problem, and I didn't see it because I thought I knew what all of those hotkeys were.

Thank-you for your patience in helping me.

I can't think of what other things I can kill from my system tray.  I have killed everything I see but Alfred.  I will see if there are any other apps interfering.

It isn't two workflows that causes the issue.  It is when Alfred itself is activated by Command+Space, and in the case of this example a workflow or other system hotkey is assigned Command+Shift+Space.

An excellent way to reproduce this problem, entirely within Alfred v2, is to assign Command+Space to activate Alfred and then to try to create a Workflow with a hotkey of Command+Shift+Space.

When I assign Cmd+Space to Alfred v2, the system level hotkey Cmd+Shift+Space no longer works.  It appears the Alfred is eating the Cmd key up event.  This causes other odd keyboard manifestations in Parallels regarding Cmd.

Again, this worked perfectly in Alfred v1, but does not work in Alfred v2.