Jump to content

parekh

Member
  • Posts

    44
  • Joined

  • Last visited

Posts posted by parekh

  1. Hi there,

     

    Alfred workflow hotkeys are registered globally which is why you are seeing this [expected] behaviour. You can, however, set related apps in the hotkey preferences in the workflow so that the hotkey is only active when VLC isn't active.

     

    In the hotkey preference, select the "Related Apps" tab, then select the active option to "Don't have focus", then drag VLC into the list below.

     

    Cheers,

    Andrew

     

    Thank you very much for your response! That solves my problem completely.

     

    (EDIT) PS: Instead of putting VLC into the "Don't have focus" list, I just put my browser apps into the "Have focus" list, because those are the only apps for which I need to use this particular workflow.

  2. Hey guys, I"m facing a problem with hotkey conflict --- I'm using the shortcut cmd+opt+right for an Alfred workflow (http://goo.gl/yuEjVZ), but I'm also using the same shortcut with VLC media player. The problem is that whenever your workflow is enabled the VLC shortcut doesn't work, but when the workflow is disabled the VLC shortcut does work. Is there any way that I can use the same shortcut for the Alfred workflow as well as VLC?

     

    Thanks very much in advance to anybody who can help me with this question. Cheers!

  3. Well, yes, but that kind of defeats the purpose of the workflow. It is designed to be a super-quick way to look up the times in a bunch of cities that you regularly want to check. The "live" single lookup feature is really just a bonus add-on. It works fine, but it's a whole lot slower than the saved quicklist cities.

     

    But sure, if that's what you want to do, then go right ahead. ;)

     

    Yes, I realize that this is not the way in which you intended for the workflow to be used, but I think that it suits me quite well. I am uncomfortable with the quick list, because it requires me to always ask myself the question "has the timezone in this city changed since the last time I ran a timezone update?" and I don't want to think about this question every time I use the workflow.

     

    For what it's worth, I don't think this is your fault, and I still believe that this is an excellent workflow. The real culprit in my mind is the whole concept of Daylight Saving Time, which I find to be outdated and unnecessarily complex for today's global and interconnected world.  

  4. These instructions are all in the first post of this thread (and with the workflow).

     

    No, it's the other way round. The "quicklist" will require updating after DST changes, whereas arbitrary individual lookups will be "live" and should be always accurate.

     

    So if I empty my quicklist then I will never have to run any updates? If this is the case, then I think this is the perfect solution for me!

  5. The workflow calculates the difference between the requested city and your local time (as per your computer's clock) and stores it as an offset from your computer time.

     

    Are you doing a "live" lookup (ie. "tz place-not-saved"), or do you have Los Angeles stored in your quick list (ie. keyword "tz")? If the latter, then yes, the US has recently changed to DST so a refresh of saved offsets will have been required. If the former, then that result should be correct regardless.

     

    I'm not sure why you had to update last week and again today. The only thing I can think of is that it might have been a long time (ie nearly 6 months) since you last used the workflow so DST had expired, and then it was re-implemented just this last weekend.

     

    Perhaps in a future update, I'll be able to store the DST change dates with the saved cities and automatically account for it or, at the very least, remind the user to manually update. I'll see if I can find some time to have a look at that in the near future. Thanks for your input.

     

    Thank you very much for following through on this issue with me; I really appreciate it. Just one final question: you mentioned something about a quick list. Could you please let me know how to check which cities are currently stored in my quick list and how to add more cities to this quick list? 

     

    If I understand you correctly you're saying that the time for quick list cities will ALWAYS be accurate regardless of whether or not I have recently run a timezone update. Is this correct? Thanks.

  6. You only have to do it every six months, and most of the world changes to DST within a couple of weeks of each other. In fact, for live results like the one in your example, you would only need to update when YOUR location changes to or from DST.

     

    Yes, it's a little cumbersome, but that's what allows the main workflow list of cities to be so fast — the timezone offsets are stored locally. If it had to check the current offset for every saved city every time, the list would be a LOT slower.

     

    Thank you for your message, but I'm having some difficulty understanding what you're saying. How does it depend on my city or my location? Doesn't it depend on the target city? I actually came here because I've run into the same problem again. Here's a timeline of my problem:

    • March 5: I want to know the time in Los Angeles. The information displayed is incorrect. I have to run the timezone update to fix the problem.
    • March 10: Once again, I want to know the time in Los Angeles. The information displayed is incorrect. I have to run the timezone update to fix the problem.

    Between March 5 and March 10, there was no change in my time zone. I have been on Central European Time for this entire duration. The only thing that changed was the time zones in the United States. So I'm not sure how any of this depends on my city or my location. 

  7. This is almost certainly due to a daylight savings change in either your city or the city in question. Just run an update "keyword: timezone update" to refresh the workflow's list of city offsets and it should be correct again. (FYI, LA is showing up as PST for me.)

     

    Cheers.

     

    Thanks. After I ran the update "keyword: timezone update" the problem was fixed. But it's a bit cumbersome to run this update every time I want to check the time in some city.

  8. Something is wrong with this workflow. I just looked up the time in Los Angeles. The correct answer is supposed to be 9AM PST. But this workflow shows the answer as 10AM PDT.

     

    Screenshot: http://imgur.com/LreeK7X.png

     

    As you can see in the screenshot, this workflow is clearly showing LA to be on PDT, but LA is supposed to be on PST until March 10. I looked it up on the World Clock (timeanddate.com) and their information seems to be accurate.

     

    I used to love this workflow, and I really appreciate the effort that has been put into this, but I cannot continue using it if such errors persist. 

  9.  

    Thanks very much for this workflow, but I would like to point out one bug that I've discovered, and I'm wondering if there's any way to fix it. The output of this workflow (whatever gets copied to the clipboard) contains a superfluous line break following the url.

     

    The expected output is:

     
    But the actual output is:

     

     

     

     

    Thank you. I'll fix it ASAP.

     

     

    Hello! I just wanted to remind you that this issue still has not been fixed. I was wondering if you are still planning to fix it? In any case, thank you once again for this excellent workflow.

  10. try to remove the AppleScript entry in Manage API clients, and restart your Skype

     

    Manage-API-Clients.png

     

    Have you got the newest version of the workflow? http://guiguan.github.io/Uni-Call/

     

     

    Hey, thanks for your quick response! It didn't work at first, but then I repeated the process a few times and now the notification seems to have gone away.

     

    About your new workflow - I saw it, but I didn't download it because I don't use Amego or FaceTime (I only use Skype). Should I get your new workflow anyway?

  11. If you disable "Open contacts in Alfred" in Feaures>Contacts> it will open just by hitting enter, which is even faster.

     

    Thanks for the suggestion, but unfortunately that's not my desired functionality. I would like the following functionality:

     

    return: open in Alfred

    cmd + return: open in Contacts

     

    (I just feel that cmd + return is more intuitive than cmd + o).

  12. Thanks for creating this workflow, but unfortunately it doesn't work for me. When I search for a contact's phone number in Alfred and press return, the phone number just gets copied to the clipboard.

     

    When I type in "call phone_number" it dials the wrong phone number.

×
×
  • Create New...