TFF Box 1.0 doesn't know how to find apps
When I launch TenFourFoxBox 1.0 it says it can't find '/Applications/TenFourFox7450.app'.
Well I never store apps loose in the Applications folder. Mac OS X has ALWAYS supported finding apps up to 3 levels deep in subfolders as a built-in function of the OS, so clearly your app is trying to "roll its own" in a very braindead way. This is the only time I have ever seen such a silly error message on my Mac.
Please fix. Thank you.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Cameron Kaiser on 23 Jun, 2016 12:54 PM
Given that the app needs to find the most recent version and the proper one for the architecture, I'm not redesigning the search mechanism to suit your particular desire about where the app should be located. I don't find anything unreasonable about looking in a default location, and I also don't appreciate snide bug reports on software that didn't cost you anything.
I wish you luck with another software product.
Cameron Kaiser closed this discussion on 23 Jun, 2016 12:54 PM.
Boodlums re-opened this discussion on 23 Jun, 2016 01:44 PM
2 Posted by Boodlums on 23 Jun, 2016 01:44 PM
I'm sorry it came across as snide or ungrateful, but if you don't find anything unreasonable about looking only in a default location, then you do not understand the Mac at all. Such app behavior might be acceptable on Windows, but it is NOT acceptable on the Mac. I've been a Mac user for nearly 30 years, so I know what I'm talking about. If you don't want to change your search mechanism, you could at least offer to let the user navigate manually to the desired app if it wasn't found programmatically.
3 Posted by funtoosh on 24 Jun, 2016 07:33 AM
… ever tried using an alias of TFF in /Applications?
4 Posted by Boodlums on 30 Jun, 2016 12:59 PM
Indeed, that was the first thing I tried! Didn't work.
And I guess I lied slightly—this wasn't the first app to behave so un-Mac-like; I seem to recall it happening once before, many years ago.