Andrew

Update: I'm currently working on a generic fix, as this turns out to be a more holistic issue than framework / JSON. Shouldn't manifest itself much, but better to be safe than sorry

@surrealroad sorry about the delay on this, I haven't had a dev setup on High Sierra so haven't been able to looking into this with more detail. It looks like Apple's framework or JSON parsing has changed a little, and where Alfred is expecting a string for the "arg" field, you are passing an integer. Before High Sierra, Alfred would happily take any object type and fall back onto the objects description, in terms of e.g number -1, that would be "-1" as a string. This no longer seems to happen. I'm going to look a little deeper into this and likely create a workaround or fix, but in the short term, you can fix this by returning "-1" instead of -1 for the arg. (For reference, the JSON format is here: https://www.alfredapp.com/help/workflows/inputs/script-filter/json/)

@ascandroli @vitor could you please update to the b871 pre-release and let me know

Ah no worries, I can see what I've done (in fettling with the match field). I'll get a new pre-release out shortly!

Hmm I'm not seeing this in my test filters, but this whole area has been worked on. If you add the Script Filter getting started workflow, does it work as expected? Under what set of conditions / options in the Script filter are you seeing this issue?

@GuiB This is now fixed if you update to pre-release b868

@surrealroad My test workflows are working on 10.13 Beta 7. Are you seeing any errors in the Alfred debugger (set to All Info), or in Console.app? Are any of your Script Filter workflows working (especially non-JS script filter ones)?

@GuiB Doh, sorry 'bout that! This is why I have pre-releases I'll make sure it doesn't show anything if rerun isn't present in the next release.

@GuiB Yep no probs, I've updated it to accept one or more files for the next release Also, interesting what @deanishe said - For some reason, I was fully resolving paths and symlinks on the receiving code. I've changed that to just standardise paths instead (i.e. resolve ~/).

The Alfred 3.5 pre-release adds new 'browse' and 'action' alongside the 'search' AppleScript commands. Use search to populate Alfred's search field. Use browse to populate Alfred's file system navigation path. Use action to show the actions panel for the given file. Cheers, Andrew

@s4nji This should now be sorted in the latest 3.5 pre-release

@GuiB If you update to the 3.5 pre-release, dynamic configuration using JSON should now work (the bottom one in your example workflow). Note that you could actually get rid of the ArgVar object in that flow and put the {query} directly into the value field in your JSON Config object. I still haven't gotten around to being able to use variables directly in complex tables such as the file filter fields section, but this is planned. Cheers, Andrew

This should now be fixed in the 3.5 pre-release. If you have a mod defined in the Script Filter JSON but with no [mod] related connection, Alfred uses the "don't close" setting from the default connection. Cheers, Andrew

@GuiB If you update to the 3.5 pre-release, the app-contextual hotkeys should work properly

If you update to the 3.5 pre-release, you'll find the new Bookmarks feature in Alfred's Feature preferences. Note that at this point, Google Chrome is default profile only. Let me know how you get on Cheers, Andrew

@vitor I'm going to move this to noted. It's actually a pretty tricky thing to fix as Alfred knows it's a dead key you've entered, but macOS doesn't pass Alfred what that virtual dead key should look like, so I can't easily show a string representation for it. It may have to remain a known issue for now. Cheers, Andrew

@jchook I just set Alfred to automatically run a couple of thousand show / hide cycles on both my Macs and haven't been able to reproduce this issue. Also, this hasn't been reported by others, and the Console info doesn't look related to Alfred. Could you have some defunct or hung network drives which could indirectly be causing an issue? Have you tried temporarily creating a new user profile on your Mac and seeing if it's reproducible there? Cheers, Andrew

@GuiB A simple use case... A hotkey wired to take the selection and run a script with it (doesn't matter what). When triggered with Alfred visible on the selected item in Alfred's default results, or Alfred's file system navigation, Alfred hides - this is just the behaviour (wether right or wrong). If a user is expecting this action to happen, and have setup their workflow expecting this to happen, changing the behaviour could break their workflow. I know this could be fixed with adding a 'hide Alfred' object, but that makes it a regression. On another note, I've done a one line code fix which changes internal window event order, so this is essentially fixed now (even though it still flickers).

@GuiB the focus is with Alfred, but because of the conflict I noted above, Alfred's hotkey manager has de-registered the hotkey so it's no longer active. There are a few options for fixing this. The one I'm considering would be to make Alfred not hide when a simulated cmd+c happens, which would be nice as you also wouldn't get a flicker when doing what you want. The down side of this is it may cause regression if somebody is using a hotkey with macOS selection and relying on Alfred from hiding for their action.

@GuiB Ah sorry, I mis-read your issue - you actually WANT to use these hotkeys within Alfred; yeah this should work hm. Looking a bit deeper into this, I can see what is happening. Alfred simulates a cmd+c when getting the selection in a hotkey and picks up the content. When Alfred is showing and you manually use cmd+c, Alfred automatically hides so you can use what you've copied - These two actions obviously interfere. When Alfred is re-showing again, in some circumstances (e.g. browse in Alfred), the code I have which makes Alfred (being a floating panel instead of a window) be noticed as the active application isn't being correctly run.

@GuiB All of those hotkey objects are configured to only be active when Alfred is active. macOS window focus identification can be a little weird with floating panel windows such as Alfred, which may be why you are seeing weird behaviour.

Interesting, and a simple logic issue to fix in Alfred's framework. Essentially, when deciding if Alfred's window should close, I hadn't taken into account a mod override with no matching mod connection needing to use the default connection "don't close" state. The reason this is manifesting when using quicklook is a little more bizarre. It looks like macOS shifts the focus differently after QuickLook which means when Alfred is hiding for a fraction of a second after using quicklook (because the logic above was broken), the timing prevents Alfred from continuing to be visible. Either way, nicely spotted @GuiB - this will be sorted in the next pre-release! Cheers, Andrew

@deanishe at this point of development, it's just loading default profile, but I've already planned multiple profile support. To save me a little time when I get to that, do you know where the list of all profiles, and current active profile is defined?

Quick update on this: I've nearly finished a new feature for the next release in which Alfred indexes the bookmarks rather than using macOS metadata. This has allowed me to add in indexing for Google Chrome too, plus adding additional nice features such as searching via folder name, host name and title. I've also added the ability to open all bookmarks in the default browser, or the respective source browser. I have other things to do for this release, but it shouldn't be too long until this is in pre-release. I've unlocked this thread for comments, but please don't keep bumping it. Cheers, Andrew

@Yosinto there may be some defunct metadata somewhere which is why duplicates are being shown. If you right arrow to bring up the actions panel for the contacts and reveal them in finder, you can see where they originate from. Anything outside of ~/Library/Application Support/AddressBook is probably defunct, but there could also be stale data within this folder. Cheers, Andrew