Search the Community
Showing results for tags 'menubar'.
I'm a heavy user of Bjango's iStat Menus, using it to check my system stats frequently. I also happen to be a heavy Alfred user, making my mouse trips up to the menu bar for iStat Menus feel really infuriating. I'd ideally like to open iStat Menus menu bar items using Alfred keywords. For example, if I type in "cpu" in Alfred, it will open the CPU stats from the menu bar, "ram" for "RAM", etc. I've searched everywhere for a workflow like this but can't find anything. I've conducted some research, mostly around how to get a readout of what menu bar items are called by the SystemUISe
Hi, I've created a basic workflow that searches the system's menu bar. After having used Sublime Text's command palette I wanted to have a similar system-wide functionality. EDIT: For people that haven't worked with Sublime Text's command palette: the command palette allows you to fuzzy search the entire application menu by keyboard. This saves both time on hunting down the right menu and saves you having to remember all sorts of keyboard shortcuts. For a brief introduction on Sublime Text's command palette see https://tutsplus.com/lesson/the-command-palette/ EDIT: Better use ctwise's
It is my first Alfred Worklfow - especially first bash I've ever wrote for a reason deserves to share with people. As you know, BitBar is a cool plugin which helps you to manage your Menubar. At last 3 weeks - I was crazy busy by dealing with tens of different things in an hour. That is why I create this script to manipulate BitBar Plugin text by using Alfred Workflow. Installation is not easy but I'll help you: Install BitBar first. Create a directory under your Documents/BitBar-Plugins, move .sh file into this (~/Documents/Bitbar-Plugins/write-into-menubar-bitb
Hey I'm trying to make an AppleScript to be run from Alfred, that should quickly set a specified speaker as audio output device if it is currently connected (in example below "My Awesome Speaker"), and otherwise don't do anything. I have gotten most of the functionality down (toggling between speaker/internal speaker), but I'm having a problem in the instance that the speaker isn't connected. When this is the case, the script has already clicked on the audioMenu, making the dropdown be there until a mouse click. I thought I could make it go away by branching with an "if