Jump to content
nikivi

Keyword activated from external trigger fails to activate [Fixed 4.0.2 b1085]

Recommended Posts

Posted (edited)

I have a workflow that has a keyword trigger that I activate with external trigger.

 

Activating it from keyword works (pressing enter):

 

887017595_2019-05-29at23_55.png.27c6557a4f62b7a56808d3169b86752f.png

Activating it from external trigger (my preferred way) doesn't work:

 

1791010366_2019-05-29at23_56.png.b51ec0f394c52f1cd36287848ebaf07c.png

 

Pressing return does nothing. No logs added in Debugger too. This workflow worked perfectly in Alfred 3 but now fails in Alfred 4.

 

I really rely on this working as its one of my most used workflows.

 

Thank you.

Edited by nikivi

Share this post


Link to post
Share on other sites

From my tests the bug is not because the keyword object is activated externally, but because it has an empty 'Title' or 'Subtext'. Your "{var:empty}" get changed to an empty string, so it does the same. For now, just replacing your '{var:empty}" to any string (but only spaces since Alfred strip them) will repair your workflow.

 

So, the problem is "Getting" into a keyword object that has no Title or Subtext defined. I mean arriving to the keyword from another object won't work, but invoking it directly using it's keyword work.

Share this post


Link to post
Share on other sites
2 hours ago, GuiB said:

From my tests the bug is not because the keyword object is activated externally, but because it has an empty 'Title' or 'Subtext'.

 

That's right. IIRC, Andrew recommended doing it this way to Niki to prevent the title flashing up when activating the Keyword via External Trigger.

Share this post


Link to post
Share on other sites

@nikivi as a workaround while I look into fixing this properly (i.e. I don't want an empty row showing, but still being able to action the result), add a workflow variable of "empty" with a single space as the value. That will get you up and running for now.

Share this post


Link to post
Share on other sites

Actually I take that back. Shouldn't this not be there:

 

706553853_2019-06-07at15_50.png.ac1763273724484c78075cba4291cbff.png

 

 

855213843_2019-06-07at15_50.png.81665b4c8cb537e0e74939a61e22bd28.png


I think that was the point of the change. Now it activates but that empty thing shouldn't be there. Only Alfred input prompt.

Share this post


Link to post
Share on other sites

@nikivi For now, I wanted to revert to the v3 behaviour just to get you up and running, can I confirm that this is the case?

 

The change to make Alfred correctly act on "no results" as if there is a result requires a bit more thought as I don't want to "fudge" things in the framework.

Share this post


Link to post
Share on other sites
47 minutes ago, Andrew said:

can I confirm that this is the case?

 

It is. 

 

Should I open a feature request for clean empty external prompt?

Share this post


Link to post
Share on other sites
6 minutes ago, nikivi said:

 

It is. 

 

Should I open a feature request for clean empty external prompt?

 

No no, it's ok, I already have a ticket for it

Share this post


Link to post
Share on other sites
4 hours ago, Andrew said:

Could you let me know?


Pretty sweet. It works, thanks.

Share this post


Link to post
Share on other sites

×
×
  • Create New...