Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Disable BBEdit's 'APE' crash warning' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Disable BBEdit's 'APE' crash warning
Authored by: sjonke on Jun 13, '05 11:46:51PM

BBEdit doesn't crash. Really, it doesn't. I can't remember the last time BBEdit crashed on me. A year ago? Longer? Methinks some "haxie" (god how I hate that "term") may indeed be causing problems for you and BBEdit. Have you considered trying disabling APE and seeing what the result is? A flawed APE module can definitely cause crashes and instability. If you want to use APE without problems you have to keep up to date on it and all modules, and even then you may have problems. In spite of what they say, a hack is a hack, and hacks can cause crashes when they do things the underlying application isn't expecting, or when an application something something the hack isn't expecting.

---
--- What?



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: deleted_user18 on Jun 14, '05 01:20:56AM

Yeah right BBEdit ist the first software without flaw. Good old carbon horse. Even mathematicans proved that its code is without any bugs. Haha.

So every bug must be in APE, can't be in OS X or in some optional kernel extensions.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: Tom Robinson on Jun 14, '05 02:17:21AM

A couple of years ago I used to run FruitMenu. Both BB's Mailsmith and the Finder regularly crashed. I've since switched to Classic Menu which provides the same basic functionality but without hacking into the system to do so. No more crashes.

I know people will jump to Unsanity's defence, but the fact is it does cause problems for some people. You get that when you're hacking the system.

If Unsanity caused an increase in calls to BB's tech support because it had been injecting code into BBEdit, why not provide a warning as the first step in troubleshooting?

There was a long discussion about this on the Mailsmith mailing list, and some pretty knowledgeable guys (not from BB) berated the Unsanity people for thinking they knew better than both Apple and other app writers.

If BBEdit is regularly crashing, you're a lot better off finding the reason why instead of patching it to disable the warning.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: zot72 on Jun 14, '05 09:04:09PM

BBEdit (or Mailsmith in my case) isn't crashing for me; that's the whole problem. I've seen the damned warning countless times, and not once had Mailsmith crashed or been force quit. Because the stupid dialog is posted after a nimrod check that seems to succeed if you've ever even heard of an APE-based product, I'm left with Mailsmith repeatedly interrupting my work with a condescendingly-worded dialog telling me it is Unsanity's fault that my hardware vendor released a device driver with a hot-plug defect. Bare Bones has, therefore, tried to steal my irratation with my hardware vendor from that hardware vendor (where it belongs) and redirect it towards Unsanity. They only succeeded on the first part of that.

The hardware vendor has since released an updated driver that doesn't crash my PowerBook. Has Bare Bones released updated apps that don't post idiotic dialogs for no reason other than to piss me off? Apparently not.



[ Reply to This | # ]