Jump to content

xilopaint

Member
  • Posts

    896
  • Joined

  • Last visited

  • Days Won

    24

Posts posted by xilopaint

  1. 10 minutes ago, deanishe said:

    IIRC, this was a deliberate choice. The reasoning was that if the user rejected the update, they probably don't want an "An update is available!" notification in their face every time they use the workflow. So they will be left alone for a day. (It also prevents AW from immediately checking for an update again.)

     

    Oh, I didn't realize that it would be "silenced" for a day. I thought it wouldn't show up again unless a new release came out so I planned to suggest a "silence" feature, though in this case there's nothing to point out. Thank you for clarifying.

  2. 1 hour ago, deanishe said:

     

    AW can't know and doesn't care whether the user clicked the update button or not.

     

    All AW does is compare the version number of the installed workflow with that of the available releases. If there is a release with a higher version number, Workflow.update_available will be True.

     

    If you want more help, you're going to have to upload your workflow and log file.

     

     

    Here.

     

    The latest GitHub version is v1.0. If you have the cache cleared and change the workflow version to v0.9 the update item will be displayed. After actioning the item the update will be downloaded and you will be prompted to install the newer version. If you don't conclude the installation the Script Filter will no more display the update item unless you delete the __workflow_update_status.cpickle file.


    I assumed __workflow_update_status.cpickle file stored the version number of the latest release after the update is downloaded from GitHub and as a result the Script Filter couldn't display the update item again once the installation is not concluded by the user.

  3. 27 minutes ago, deanishe said:

     

    Yes. The list of available releases is fetched asynchronously in the background, so the cached list may be weeks or months out of date when you see an "Update available!" message if you haven't used the workflow in a while.

     

    So when you trigger an update, it first fetches the list of available releases to ensure it downloads the latest version.

     

    Ok. There's another thing.

     

    If the update is downloaded but the user for any reason doesn't click on the update button in Alfred Preferences when prompted, the __workflow_update_status.cpickle file is updated in cache folder and the user will not be prompted again unless the .cpickle file is manually deleted. Is it also expected?

  4. @deanishe, I got the self-update feature to work, but I noticed in my tests that the script has to run twice in order to download the update. In the first run __workflow_update_status.cpickle and gh-releases-{github_slug}.cpickle are saved in the cache folder. Only in the second run the update is installed. Is this expected behavior or I'm doing something wrong?

  5. 16 hours ago, nikivi said:

    At least I have learned the lesson of not posting images instead of workflows.

     

    lol

     

    nikivi is one of my favorite internet trolls. I really appreciate his cynical sense of humor. It's a funny character undoubtedly.

  6. Yes it does. Btw, it's a case in which the translation was made literally. In most cases the "translation" for the Brazilian market gives some really stupid titles to the movies.

     

    "The Hangover", for example, was translated as "If you drink, don't get marry".

     

    "Lost in Translation" was translated as something like "Matches and Mismatches" (the idiot was literally lost in translation).

     

    They have to "translate" even a title that is a character's name like "Annie Hall", "translated" in Brazil as "Neurotic fiance, nervous bride".

     

    A ~tech related~ case is "Fear Dot Com", translated to Brazil as "Fear Dot Com Br" (yes, as it were not enough ridiculous adding the "Br", the genius forgot to include one more "Dot" to make "Dot Com Dot Br").

     

    So I think you don't have much to complain about the English movie titles. lol

  7. 7 hours ago, deanishe said:

    In that vein: do you know a search phrase I can use to check whether I'm getting Brazilian results vs Portuguese ones?

     

    I can hardly tell Portuguese from Spanish, let alone the difference between dialects. 

     

    Can it be a word? If you try canalizador you will have mostly plumber related videos in pt-PT results and mostly random results in pt-BR.

     

    If you type the letter v, PT-pt results will display a hip hop Portuguese singer in the first result:
     

    r8sRXRl.png

     

    But not in pt-BR in which a trending Brazilian song (a terrible one) is displayed in first place:

     

    RphHNw0.png

  8. 36 minutes ago, deanishe said:

    Contacts.app formats numbers for display. What you see is not necessarily what's actually stored in the database.

     

    Find a contact that's correctly formatted in Contacts.app, but not in Alfred, and edit it in Contacts.app. I think you'll find that what Alfred shows is what you've actually written in the phone number field. 

     

    In fact if you edit the phone number field by removing only one character and reinserting it immediately you will have the phone number correctly formatted in Alfred in the same way as Contacts.app.

  9. 23 hours ago, deanishe said:

    I've pushed an updated version to the develop branch with GOOGLE_PLACES_LOCATION and GOOGLE_PLACES_RADIUS options in the workflow configuration sheet. You must set both for it to work, and the location must be in decimal format, e.g. 51.450833,7.013056, and the radius is in metres.

     

    Hey deanishe, I have built the workflow from the source folder, as the binary file was not updated by you in GitHub, and can't see these options in the configuration sheet.

  10. On 9/11/2017 at 9:01 PM, ae6dx said:

    Can anyone help here?

     

    It's a known issue with macOS Contacts API which is used by Alfred.

     

    Two years ago @Vero mentioned in the following post that they had a ticket to address the issue in a major version, but the fix didn't come out yet.

     

     

  11. On 1/9/2017 at 0:35 PM, deanishe said:

     

    Google Maps API is gone. I have a working replacement using the Google Places API, but you need an API key to use that one.

     

    Version 2 in the develop branch has working Google Places, but doesn't support many other engines yet, as I still haven't decided on the right data model/JSON format. Install at your own risk.

     

    I have been using version 2 and got a key for Google Places API Web Service, but the search doesn't take my location into account, so I have to type my city's name. Is this the expected behavior?

×
×
  • Create New...