Jump to content

Andrew

Creator
  • Content Count

    3,616
  • Joined

  • Last visited

  • Days Won

    126

Everything posted by Andrew

  1. If you type 'preferences' into Alfred, you'll get "Show Alfred's Preferences" in the results.
  2. @Fira It's part of "Advanced Date Formatting using Unicode formats" which links to this page: http://www.unicode.org/reports/tr35/tr35-31/tr35-dates.html#Date_Format_Patterns The formatting itself is a unicode standard, there are plenty of examples on that page. I'll add a note to add more examples on our own help page Cheers, Andrew
  3. @h2ner if you pass some text out of a Run Script (i.e. the open file you've looked up), then it can be set to a variable in the Arg & Var (set the name of the variable, and set the value to {query}). The variable is then available to subsequent scripts (i.e. the Script Filter) as an environment variable. As you've said, this is a much cleaner way than adding some configuration. Cheers, Andrew
  4. @Fira Here are a few which should help out: 24h formatting without am/pm: {date:HH:mm} 12h formatting with am/pm: {date:h:mm a} Let me know how you get on Cheers, Andrew
  5. @mickaphd take a look at the permissions section here: https://www.alfredapp.com/help/getting-started/macos-mojave/#integration Specifically the "Full Disk Access" Cheers, Andrew
  6. I've been playing with this a bit today, and it's actually quite a tricky conundrum when everything is taken into account. Alfred stores the string at the point of setting the hotkey as this is presented to him from the API, but to map a string key value back from a keycode is not a trivial task involving UCKeyTranslate. I'm going to contemplate the best approach to this, but it might have to be an alternative display mode which shows the original and translated codes.
  7. @d3v1an Alfred has no control over this process with 1Password 7. Alfred has a bare minimum of information about the login just to display the name to you, and when you select this login, it's passed to 1Password to handle opening the website, and filling your details. It might be worth posting on the 1Password forum to see if they have any ideas about this... perhaps (but probably not) they should be aware of intermediate browsers such as Choosy, or perhaps they could have an option to force which browser (e.g Safari) the logins open in instead of the default browser (i.e. Choosy on your Mac). You could possibly create a fudge workflow to switch your default browser, but then you'd need some way of browsing your logins in a Script Filter, which would require a fair amount of scripting to interact with the 1Password 3rd party data. Cheers, Andrew
  8. @AXLr80r can you paste in the metadata for an app you're looking for instead of Alfred 3.app - Alfred, by design, does not find his own app package.
  9. I have something in the works which I think will make you very happy with regards to this. That's all I'm saying for now
  10. @GingerbreadMan I'm seeing the same error in ScriptEditor:
  11. @hecate Alfred evaluates dates based on unicode tr35: So you'll need to use the following for your initial example: {date:yyyy-MM-dd, HH:mm} For the full current month name, use: {date:LLLL} This link covers all other formatting you'll need: http://www.unicode.org/reports/tr35/tr35-31/tr35-dates.html#Date_Format_Patterns Cheers, Andrew
  12. @yeagerfan if you update to the latest 3.8.1 pre-release, this is now fixed
  13. @billiesoniq scroll down past "Full Disk Access" in the Security & Privacy prefs, and under "Automation", make sure iTunes is ticked for Alfred. macOS should have asked automatically for you to grant this access, but if you missed the popup, it may have been left unticked, preventing Alfred's access. Cheers, Andrew
  14. @gentle_md that beta is 3.5 years old and long retired, just use the latest version of Alfred
  15. @Anton Patrushev if you set Alfred focusing to "compatibility mode" in the Appearance > Options preferences, then Alfred will behave like a traditional window rather than a (Spotlight-esque) panel. BTT should then be able to see window changes. Cheers, Andrew
  16. @deanishe hmmm I seem to remember there was a reason I used the NSWorkspace method instead of NSFileManager one, but can't find anything in my notes. It may have been a legacy thing... To be honest, until you said that, I had forgotten that NSFileManager even had an unmount method! I'll have a bit of a dig Edit: Aha... that method is newer than I thought, macOS 10.11+, so it's more tricky to include as Alfred 3 supports older versions than this. Cheers, Andrew
  17. @deanishe The error which is returned to Alfred after the NSWorkspace call only goes as far as Error Domain=NSOSStatusErrorDomain Code=-47 "fBsyErr: File is busy (delete)". With a quick look, I can't see anything obvious to get more info within the API, but I'll make a note to look into this when I get a bit more time.
  18. @yeagerfan I have a fix in for this already for an upcoming 3.8.1 release - it's to do with a change in the way eject errors are being dealt with. Cheers, Andrew
  19. @nikivi Okie! I don't see a problem with that... I'll see what I can do
  20. Interesting reading this thread - I'll add a note to remove the constraint there which prevents you saving when the title is empty, as I imagine that it has existed from before you could wire things into a keyword object. In the case of being a direct input (i.e. being show from an inbound connection), and there being no title, would you prefer there to be no result shown at all, just an input box? (instead of an empty result). Cheers, Andrew
  21. @politicus put the absolute path to shuf, wherever you have it installed. Cheers, Andrew
  22. @Flyshewoorst yes, I added a QWERTYZ keyboard layout, created a new project in XCode adding a local monitoring for events in the way you described, and watched the events coming in. When typing cmd+alt+# on the QWERTYZ keyboard, I see keycode 42 coming through as expected when Alfred is or isn't running. This mixed with the fact that Alfred doesn't alter macOS level events means there is nothing I can do to fix this. Perhaps try temporarily creating a new user account and try your tests there. It could be that there is an underlying configuration or app on your profile which is inadvertently causing the unexpected behaviour. By trying this on a new user account, you'll get default behaviour. Also, is your keyboard a standard macOS keyboard, or do you have a 3rd party keyboard?
  23. I've been trying to reproduce this issue this morning, and other than 1Password assume the hotkey alt+cmd+keycode 42 which is cmd+alt+\ on my keyboard, I quit 1Password and I have not been able to reproduce the issue you describe. Is there a specific reason you're using NSEvent.addLocalMonitorForEvents instead of using the Responder Chain which is the default and recommended way to interact with key events within your app? I'm changing the title and moving this out of Alfred bugs.
  24. @Flyshewoorst The only event tap Alfred uses is for snippet auto-expansion, and this is a read only view over the events for observing key patterns matching snippet keyword strings. At no point does Alfred directly alter lower level events, so there is no way Alfred can be directly altering the events in the way you describe. Could you provide a little more information on what you're experiencing (perhaps a step by step, as I can't see how to reproduce what you're trying to explain), and perhaps what you're trying to do yourself, as this may help point to why you are experiencing oddity. As you've seen in the global monitor, there isn't an issue, so it could be something to do with the way you're interacting with your local tap. Also, do you have any other apps installed which may be causing events to be changed (even in relation to Alfred), such as Karabiner. Andrew
  25. @onewheelskyward are you on the general release of 3.8 (build 959)? If not, update to this and things should work. If still not working, and if Finder and Terminal are selected in the Automation settings, then try restarting your Mac. In one of the 3.8 pre-releases, I had updated to Xcode 10 without adding the required NSAppleEventsUsageDescription for automation, so if you updated through that pre-release, it may have confused your Mac. Cheers, Andrew
×
×
  • Create New...