Console message - supply a value for ThreadSafe

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Look at console logs, search for SIMBL

What is the expected output? What do you see instead?
Probably nothing?  I don't know.  This shows up for the app launches after 
SIMBL Agent, Finder in 
this case:

9/15/09 12:25:43 PM Finder[135] Performance: Please update this scripting 
addition to supply 
a value for ThreadSafe for each event handler: 
"/Library/ScriptingAdditions/SIMBL.osax"

What version of the product are you using? On what operating system?
SIMBL 0.9.5

Please provide any additional information below.
There's stuff about it here, it's a 10.6 thing apparently:
http://developer.apple.com/mac/library/releasenotes/ScriptingAutomation/RN-
AppleScriptSL/index.html

Original issue reported on code.google.com by bck...@som.umass.edu on 17 Sep 2009 at 10:31

[GoogleCodeExporter]

This is still present in 0.9.6b.

Original comment by jonlat...@gmail.com on 18 Sep 2009 at 2:58

[GoogleCodeExporter]

This is a dopey cosmetic issue -- the warning is 100% spurious. 

The event handler used in Snow Leopard is correctly labeled as thread-unsafe.  
The problem is that this warning 
is about the event used for Leopard - which is completely unaware of thread 
issues. I can't figure out how to get 
it to be backward compatible and stop complaining, so I'll let it complain.

Original comment by ms...@gmail.com on 20 Sep 2009 at 2:12

• Changed state: WontFix

[GoogleCodeExporter]

Why do you still need the SIMeleop "Leopard event" in the OSAXHandlers 
dictionary ?
I thought that SIMBL 0.9.+ was Snow Leopard only.
Am I wrong ?

Original comment by jerome.f...@free.fr on 28 Sep 2009 at 10:00

[GoogleCodeExporter]

Yes, you are wrong.

0.9.x is backward compatible with Leopard on x86 or PPC.

Original comment by ms...@gmail.com on 29 Sep 2009 at 5:42

[GoogleCodeExporter]

Issue 14 has been merged into this issue.

Original comment by ms...@gmail.com on 29 Sep 2009 at 5:45

[GoogleCodeExporter]

Issue 16 has been merged into this issue.

Original comment by ms...@gmail.com on 4 Oct 2009 at 3:35

[GoogleCodeExporter]

For those interested in a workaround: You can edit the 
SIMBL.osax/Contents/Info.plist and remove the SIMeload  string (it is twice 
there, both as a dict and as a string) from OSAXHandlers / Events.

Patch: 
https://github.com/albertz/simbl/commit/93772b8cf1bcadcf58f9fa3679d735a938394fb7

Original comment by albzey on 27 Aug 2011 at 3:57

[GoogleCodeExporter]

Sorry, it is not twice there, I misread that. It is the string SIMeleop.

Original comment by albzey on 27 Aug 2011 at 4:01