Jump to content

Jasondm007

Member
  • Content Count

    168
  • Joined

  • Last visited

  • Days Won

    5

Jasondm007 last won the day on January 10

Jasondm007 had the most liked content!

About Jasondm007

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks @dfay! That sounds amazing!! If there's anything I can do to help test etc., please let me know.
  2. @dfay By chance, do you know if your workflow for searching open Finder tabs and windows is generalizable to other apps whose menus also list their open windows or tabs? The reason I ask is because I was hoping to apply your approach to the Preview app, too. When I’m writing/researching I often have several different PDFs open in Preview - and often across more than one space/desktop and monitor (similar to the way I leave several Finder tabs open to folders that I’m working on). As a result, it’s often difficult to find the one that I’m looking for. To date, I’ve tried several different app and window switching applications (e.g., Witch, Contexts, etc.). However, they all have certain problems or quirks in this work environment. Most often, they fail to register Preview and Finder windows, which is why I reached out about Finder in the first place. I’m sure there’s no perfect solution, but since your Finder tabs workflow doesn’t seem to have any of these problems, I was hoping to do the same thing in Preview (i.e., as a separate workflow) - which has a similar approach to Finder when it comes to listing windows in its own menu. However, after duplicating your Finder Tabs workflow and slightly amending its scripts for Preview, I haven’t had any luck getting it to work. Initially, when it didn’t work, I did a little digging and found blogs complaining about Preview’s lack of AppleScript support. However, these posts were all quite old. In fact, when testing, I noticed that some of the things that they complained about actually worked just fine now (e.g., like the ability to simply close a window, etc.). Before I spend a ton more time trying research why my changes to your workflow don’t work, I was just curious if you thought your approach to Finder would also work for Preview? Thanks!
  3. @dfay After using your "Finder active tabs" script in the office for a few hours this morning, this workflow has made things so much easier for me. I just wanted to say thanks again! The script is amazing, and I really appreciate you taking the time out to create it.
  4. @dfay You are a Finder wizard! You have saved me so much time staring at Finder windows!! I can't thank you enough. Honestly, this is great!!
  5. @dfay Since you have a ton of great Finder workflows, I figured you'd be the right person to ask: Do you have a workflow - or know of another's workflow - that displays and searches for open Finder tabs? I often have several tabs open in the same Finder window, and am just looking for an easier way to get to the right one quickly (i.e., without having to squint to read the small print when they're smashed together). I was hoping it would operate like the many Chrome and Safari tab searching workflows that people have created. As a novice, this seems like it would be easier to accomplish in Finder than it is in Chrome or Safari - since, among other things, Finder's tabs are actually listed at the bottom of the Window menu - but what do I know! I haven't been able to find any posted to this forum or elsewhere, so perhaps it's a bit more complicated. Ha Thanks for any help you can lend!
  6. For those who come across this post in the future, and who are looking to do something similar, I’ve uploaded a new version of the test workflow described above here: https://cl.ly/fe0cb259c299 It’s updated to show the two different ways you can accomplish what’s described above. All of the usual caveats apply. Here’s a screenshot of it: The old approach - shown in yellow above - relies on the JSON Config utility (which now works again, thanks to @Andrew). And the new approach - shown in red above - accomplishes everything through the File Filter itself, and by adding the asterisks * directly to the Arg & Vars utility. It will only work if you're using Alfred 4.0.2 or newer. As for the new approach, here’s a few screenshots of the relevant utilities’ settings: File Filter - New Approach Arg & Vars - New Approach (old approach simply excludes the *) Hope this helps!
  7. @Andrew Thanks for the clarification on the JSON Config utility! In past attempts to fix the workflow after the upgrade I had mistakenly used the curly brackets {} and not the parentheses () with query, which explains why it didn't work. Also, thanks for the File Filter update in 4.0.2. It works perfectly without the JSON Config utility! It's a million times easier now!! Unrelated to this thread, but thanks for fixing some of the dark mode-related quirks in 4.0.2. It looks great! Thanks again for all of your help, and attention to everything! Honestly, I don't know how people work without Alfred. Hope you have a great weekend!
  8. In Alfred 4, were there changes made to the way the JSON Config utility works with File Filters? I have a workflow, that relies on these elements, that now behaves differently after the upgrade. However, I suspect that the workflow was never configured appropriately in the first place, which is why I have not posted this as a bug. In short, this part of the workflow feeds a variable for a Finder tag/label from the JSON Config utility into a File Filter. It also feeds an argument (for an asterisk *) to pre-populate the File Filter's results in a manner that makes them visible to the user in Alfred's search bar (i.e., for those of us who need a gentle reminder about which files include the tag). Unfortunately, since upgrading to Alfred 4, I am no longer able refine or narrow the File Filter's displayed search results by adding more text to Alfred's search bar. The File Filter just spits out the results for the tag/label and does not respond to any text that is added while the results are displayed, which might otherwise narrow the results. Example w. Config To explain, consider the following example for a tag with the value “Yellow” from Finder. The JSON Config utility includes the following code (where the variable “tag” is defined in earlier stages of the workflow and can take on any value, such as Yellow): { "alfredworkflow" : { "arg" : "*", "config" : { "fields" : [ { "field" : "kMDItemUserTags", "split" : false, "not" : false, "value" : "{var:tag}", "words" : true, }, ] } } } Next, the JSON Config utility feeds to a File Filter whose settings are essentially blanked out as follows: Under both Alfred 3 and 4, when triggered, the Filter spits out results that look something like the following: Now, say I’m looking for the “Pooled” Excel file in the results from above. In Alfred 3, if I typed “Pooled” in the search bar, it would narrow the results down accordingly. However, now in Alfred 4, the results no longer narrow when adding additional text - as shown in the screenshot below. To be clear, since the JSON Config utility doesn’t contain any field-related information and the File Filter is essentially blanked out, I've never understood what fields Alfred 3 used to narrow its search results (though it looked like it was using the title). But it always worked like a charm!! If I had to guess, I’d say that Alfred 4’s new sorting options are impacting it. But, to be fair, I’m not sure that the workflow was ever setup correctly in the first place. Does anyone know how to change the JSON config or the File Filter so that it behaves in the same way that it did in Alfred 3 (i.e., to further narrow its results, as described above)? I tried toying with both elements of the workflow but have not had any luck. For testing purposes, I have created a small workflow that includes the relevant portions described above, and uploaded it here: https://cl.ly/0d64ceb966bc It is not the full workflow - which is specific to my odd Finder tags/labels, and contains a few additional steps. In any case, it should help get the ball rolling if my description above is a little tough to follow. Thanks for any help you can lend!!
  9. @deanishe Thanks! Yeah, maybe it's a Mojave thing? I gave the Clipboard Viewer app a try, and boy is that thing confusing! In any case, here are my settings for the text, as it appears in Notes w. the same text as above: {\rtf1\ansi\ansicpg1252\cocoartf1671\cocoasubrtf500 {\fonttbl\f0\fnil\fcharset0 AppleSystemUIFontBold;\f1\fnil\fcharset0 AppleSystemUIFont;} {\colortbl;\red255\green255\blue255;} {\*\expandedcolortbl;;} \deftab560 \pard\pardeftab560\partightenfactor0 \f0\b\fs34 \AppleTypeServices\AppleTypeServicesF2293774 \cf0 Title Text\ \pard\pardeftab560\slleading20\partightenfactor0 \f1\b0\fs24 \AppleTypeServices\AppleTypeServicesF2293774 \cf0 \ \pard\pardeftab560\sa40\partightenfactor0 \f0\b\fs28 \AppleTypeServices\AppleTypeServicesF2293774 \cf0 Heading Text\ \pard\pardeftab560\slleading20\partightenfactor0 \f1\b0\fs24 \AppleTypeServices\AppleTypeServicesF2293774 \cf0 \ Body Text}
  10. Hi @deanishe and @dfay - OK, please ignore my previous post. After doing some more goofing around, I was able to find something that works on my system. Thanks again for all of your help! To be clear, I have no idea why it works, and the other tests did not. However, if others would benefit - and presumably have similar Notes settings - here's what worked for me in Alfred: PS - Each is designated as a "System Font" PPS - Just to be clear, the text does not look this way in the Notes app when the snippet is used. It's formatted in the appropriate tags - which for me is 17, 14, 12.
  11. Hi @dfay & @deanishe - Thanks for the feedback and for taking a crack at it! I really appreciate it. @deanishe I've tried this countless times today, and just haven't had any luck. So that I'm clear, are you recommending, in Alfred's snippet viewer, to change the font size as follows: Titles to 34, Headings to 24, and Body to 12 (or anything, since Body appears to be the default)? If so, are you also defining the Family and Typeface (Yours looks like Helvetica Neue - Regular)? Finally, once you trigger the snippet in the Notes app, yours automatically recognizes everything appropriately? I've tried countless variations, and my text usually comes out with Body tags - i.e., regardless whether it actually looks looks identical to the Notes app's text. However, I did notice that if the text is 34, or larger, it's usually recognized as a Heading. That said, I was never able to find the appropriate size or settings for Titles. If possible, could you share your working snippet? Just for testing purposes, I also tried changing the ⌘V shortcut from "Paste" to "Paste and Retain Style" and it didn't fix anything either (Notes - Edit - Paste and Retain Style). FWIW - it did seem to create some new problems with the color of the text, however - often pasting the text in charcoal/black so that it was unreadable on a dark background. In any case, I've switched things back to normal. Lastly, I'm not sure if it's helpful, but since we both appear to have different settings, I've included a few screenshots of my settings from the Notes app below. The first image shows my preferences in the app, and images 2-4 show what the text would look like if it were formatted appropriately. As always, thank you both for all of your help! Preferences - Image 1 Default Formatting in Notes app by tag, showing Fonts panel - Images 2-4
  12. @luckman212 I too got my hopes up about using snippets to paste appropriately styled text into Evernote and the Notes app. 🤦‍♂️ To be honest, I wasn't surprised by Evernote. It's always been flaky. At the moment, I can't even get it to accept Rich Text snippets from Alfred that aren't discolored or without some other problem (I use the app in Dark Mode). However, I was a little more surprised by the Notes app, since it's native to MacOS. Any ideas how to maintain its simple Title, Heading, or Body tags? Has anyone else had any luck using snippets with formatted text in Evernote or the Notes app? It's got to be possible to apply the appropriate tags or styles to snippet-related text - even if it's processed via another step. Thanks for any help you can lend!
  13. Thanks a ton @lycopodiopsida, @Carlos-Sz & @xilopaint!!
×
×
  • Create New...