search

tjluoma / km-omnifocus-launch-quick-entry

Keyboard Maestro macro to launch OmniFocus' quick entry, even if OmniFocus isn't running
4 stars 0 forks source link

Question about Hot Key Trigger(s) #1

Open GlennHodas opened 9 years ago

GlennHodas commented 9 years ago

In the article you wrote, the screenshot shots one hot hey trigger section in the very beginning of the KM workflow. But on the zip file I downloaded, there are two hot key trigger sections at the very beginning. Is that the way the macro is supposed to be set up? See attached screen shot.

And thanks for developing this macro! keyboard_maestro_editor

tjluoma commented 9 years ago

I have no idea why that is there but you can remove one or change it to something else if you'd like.

On Jul 21, 2015, at 12:34 AM, GlennHodas notifications@github.com wrote:

In the article you wrote, the screenshot shots one hot hey trigger section in the very beginning of the KM workflow. But on the zip file I downloaded, there are two hot key trigger sections at the very beginning. Is that the way the macro is supposed to be set up? See attached screen shot.

And thanks for developing this macro!

— Reply to this email directly or view it on GitHub.

GlennHodas commented 9 years ago

Thanks

Sent from my iPhone

Glenn Hodas Hodas & Associates

Office: (217) 391-3984 Mobile: (217) 494-1090

GlennHodas@me.com HodasAndAssociates.com

On Jul 21, 2015, at 7:20 AM, TJ Luoma notifications@github.com wrote:

I have no idea why that is there but you can remove one or change it to something else if you'd like.

On Jul 21, 2015, at 12:34 AM, GlennHodas notifications@github.com wrote:

In the article you wrote, the screenshot shots one hot hey trigger section in the very beginning of the KM workflow. But on the zip file I downloaded, there are two hot key trigger sections at the very beginning. Is that the way the macro is supposed to be set up? See attached screen shot.

And thanks for developing this macro!

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.