After I deleted "Smart Crash Reports.bundle" in /Library/
InputManagers/, I rebooted, went to AS Studio to see if there were
any problems, and guess what ? The Debugger started working. It's
been broken as long as I can remember. Every time I've wanted to
learn how to work with AS Studio since it came out, the Debugger has
never worked, and I always ended up moving on to something else.
This is awesome...
On Dec 24, 2006, at 5:27 PM, Steve Hayman wrote:
Make sure you're building a debug version of the project in order
for breakpoints to work. In Xcode you set this with Project >
Set Active Build Configuration > Debug .
This was the very first thing I checked the other day when I started
trying to learn AS Studio in earnest.
Also I don't think those messages you are seeing about Smart Crash
REports.bundle actually indicate that the app has crashed; it's
just reporting that it can't load this bundle for some reason, and
then proceeding anyway - I don't see anything that indicates your
app has crashed.
and came away without a real solution. It was close to 3 am so I was
barely awake, but came away confused as to what the solution was. I
had used Unsanity's products particularly the menu product, but they
caused too many problems with Quickeys and 4th Dimension. After
talking to the people that write Quickeys, I disabled all their stuff
and everything started working fine with Quickeys and 4D. They are
far more important for me, that the Unsanity stuff.
I agree with the Daring Fireball article, and am annoyed that
Unsanity patches the OS without asking for permission. I won't buy
their products any more.
That bundle is something that certain third-party applications
install which attempts to email crash reports for their apps back
to their authors, rather than to Apple. I don't know what app you
might have installed that included this but it would probably be
safe to remove the bundle. (Double clicking on it wouldn't do
anything; it's not intended to be double clicked; it just sits
there and waits to be loaded.)
After I wrote the original message I realized that it wasn't double
clickable, but by then it was too late. I think it was probably
Unsanity's APE, or FruitMenu.If you look at /Library/InputManagers/
there's an "info" file, and a "Smart Crash Reports.bundle". I just
deleted both of them, if it causes a problem I'll copy them from
another machine that doesn't have it. I'm not sure but I believe they
patch the original one from Apple. I'm not sure if that is correct?
On 22-Dec-06, at 8:54 PM, Bill Hernandez wrote:
I have documented some AppleScript Studio problems that I have
encountered, along with some screenshots.
Hopefully somebody might have a clue what is causing the problems.
Do not post admin requests to the list. They will be ignored.
Applescript-studio mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden