If the app has an AppleScript dictionary, it will show up in that list with the name you probably need to use to operate on it. The first thing to try when tracking down the name an app responds to is to open Script Editor and go to File->Open Dictionary ( ⇧ ⌘ O). If it does, and still doesn’t work, there are a couple of possibilities. First double check that the filename you’re listing in your Bunch exactly matches the name of the application in Finder (minus the. If you list an app to launch or quit in your Bunch and nothing happens, the app in question may have a different name in the system than it shows in Finder. See Debugging Scripts in the Advanced Scripting section for tips on tracking down issues with shell scripts. If it seems like a bug in Bunch, please let me know here. If you know which line is problematic and it doesn’t make sense, post about it in the forum. If you’re debugging the opening of a Bunch and have your Bunches set to toggle, you can avoid having to repeatedly close the Bunch by holding down the Option key while clicking the menu item, or by using Clear All Checkmarks, which will tell Bunch that the Bunches are closed without actually executing any on-close behaviors or quitting any apps.Īlso see the (log) command, which can be useful for pinpointing issues with variable assignment and execution sequence. Or just create one new, blank Bunch and copy one line at a time into it from the misbehaving Bunch, launching it for each now line until the behavior you’re trying to avoid happens, thus narrowing it down to that line. If needed, split out sections of a longer Bunch into temporary smaller Bunches and test them one at a time to narrow down any issues. If you’re having issues with a Bunch not doing what you expected, consult the Bunch Log to see if you can trace the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |