![]() ![]() Not a big issue for me, but worth noting. Important Note: The only noticeable downside to this approach is that you can no longer drag and drop files into the sidebar aliases, as you can when there's an actual folder in the sidebar. Using an alias, I can have my smb://.local/Collating/Photos/ folder appear in the sidebar as □ Collating Photos, without touching the actual folder name itself. I've got a number of network folders in my sidebar and they all have the same name "Photos" for example. Then I renamed those to include whatever emoji icons I want to help visibility, and added those aliases to the sidebar.īonus: You can make the names themselves more descriptive. I created ~/Library/Sidebar Aliases/ folder and dropped a number of aliases in there (Command-Option drag the folder). Instead you can put an alias to the folder in the sidebar, and have that alias contain the emoji. You get better visibility and much faster access.īest thing I've managed to do for easy visibility is to add emoji to the names of the folders.īut of course you likely don't want to add emoji to the folders themselves. ![]() If there are zero incidents, you can just display the normal logo.I'd love to be able to change the icons without an add-on. If so, you can change the icon to display the number of incidents. Using the Incident app as an example, when the page loads, you can make the call and see if there are active incidents. But my issue is that I need to change the icon without opening the top app I want to be able to update the icon in two occasions:ġ) When the agent loads the page, I need to run my logic to see which icon should be displayed and update it properly. The code you shared is similar to the code I had in place already and it works perfect when I click and open the top bar app. I was not aware of that limitation and that's what I was trying to use for the first page load. I think the error is coming from the instance for your background location, which doesn't support the iconSymbol property. Thanks James and Eric for your thanks for sharing this If he contradicts anything I say, listen to him. Add your logic for setting a specific symbolĭisclaimer: Eric Nelson is the pro. Open the window you want it to be on top. Double-click the script file you have edited to run it. Then, save the change by clicking Ctrl+S. Copy and paste SPACE:: Winset, Alwaysontop,, A to the file. Get ZAFClient for top bar app instanceĬonst topBar = await getTopBarInstance() Right-click the newly created file and select Edit Script. Return client.instance(topBar.instanceGuid) After closing this message and going to the SIMBL tab I see a red cirle next to SIMBL.osax but a gr. const client = ZAFClient.init() Ĭonst response = await client.get("instances") Ĭonst instances = Object.values(response.instances) Ĭonst topBar = instances.find((e) => e.location = "top_bar") Hello When installing the mySIMBL plugin I get this error: " simbl.osax install failed". It doesn't include the logic for setting a specific symbol, but I left a comment as a starting point. To get around this, you can use the client.instance method to set the iconSymbol using only the ZAF client for the top bar app instance. When you run an app in multiple locations, ZAF creates an app instance for each location. ![]()
0 Comments
Leave a Reply. |