Jump to content

vitor

Staff
  • Posts

    8,359
  • Joined

  • Last visited

  • Days Won

    690

vitor last won the day on March 17

vitor had the most liked content!

About vitor

Recent Profile Visitors

25,958 profile views

vitor's Achievements

Advanced Member

Advanced Member (5/5)

2.2k

Reputation

  1. Updated to 2024.2. macOS 14.4 stable broke searching of manual pages with man (FB13690576), so they are now retrieved by location. This alters the results list slightly, as retrieving descriptions one by one takes too long. But by showing the path in the subtitle, it’s now possible to differentiate between different manuals with the same name (e.g. for a tool which ships with the system but you have installed a more recent version with Homebrew).
  2. Updated to 2024.2. Support input and output in feet and inches (e.g. 7ft 4in).Support optional inches when given number after feet.Support ' and '' for feet and inches.Support “foot” for “feet”.Add option to output fractional feet.Add option for thousands separator.Add option for scientific notation.Add standardAtmosphere unit.Add milli, micro, nano, pico seconds.Allow lowercase L for liters symbols.Allow numbers starting with period.Allow negative numbers.Use Number Slider for fractions.Skip Script Filter as Universal Action.
  3. There’s no proper method to tell macOS to shutdown while respecting that setting. But you can use Shutdown Timer (it also works without a timer) to do it, as it has a setting to close all apps before proceeding to shutdown.
  4. More information is required to diagnose the issue. Please see the short post How to Report a Problem with a Workflow for details on what to provide.
  5. I think you might be misunderstanding Universal Actions. You shouldn’t use them to fill text in Alfred and then add a command, but to run the command directly. From your other issue, you seem to be loading Universal Actions into existing Keywords but they’re most powerful when used directly from the object.
  6. You’re conflating the List Filter Input and the Script Filter Input. What you need is to add a Universal Action object before the List Filter.
  7. It has been reported. Ostensibly, reporting an issue multiple times helps developers at Apple make a case for prioritising it. You can open a report to Apple by using the Feedback Assistant app on your Mac.
  8. That option is not available and is out of scope. The workflow uses yt-dlp, which is the tool outputting that message, you can run it in the terminal to add the necessary details. Instructions on how to do that are in the linked website.
  9. As stated, the most likely cause is that the API is down for the moment. Changes made to the shortcut are not supported, only the unmodified workflow. If you want to make a report on the upload action of the shortcut not working for you, you can use the Feedback Assistant app on your Mac to contact Apple, I have no control over their implementation.
  10. There hasn’t been any recent change, and it wouldn’t have happened without you noticing. The most likely cause is that the imgur API is down. Imgur is an external service and the upload is entirely handled by the shortcut, which is handled by Apple.
  11. Welcome @balupton, and thank you for sharing. Using the Universal Actions panel in this manner is somewhat atypical. Have you looked at the new Text View object in the Alfred 5.5 beta? It’s designed for cases like this where you want to present a lot of text to users.
  12. That’s an old version. To get the current one you need to follow the instructions above. That is because it’s using an unsigned binary. The debugger may provide a clue. That is a request that only the workflow’s creator can fulfil. You can contact them on GitHub by clicking “issues” and opening a new one with your request.
  13. That would add complexity and foot guns for a feature the overwhelming majority will never take advantage of. Most people don’t know (nor should they have to) the exact string of characters representing each model. That configuration is a popover button because it’s what makes the most sense to cover most cases. I’m open to the idea of allowing more overrides and even have several ideas in mind on how to do it. But adding hidden variables piecemeal to support an advanced feature for a handful of users isn’t a good way to develop stable software. So please first investigate thoroughly what are the exact customisations that would be beneficial for custom models and then we can make a decision on all of them at once. Some things can go in (like the custom API endpoint) while others probably won’t (e.g. a non-streaming method) but they should be evaluated in bulk so the workflow doesn’t end up like a brittle Frankenstein-type construction. Think in terms of “if there were going to be just one more version, what would be necessary to cover the bases?”
×
×
  • Create New...