#Mysimbl tab update#
#Mysimbl tab download#
#Mysimbl tab mac#

I must have changed something else at the same time and not realized it, because no matter what I set the version to, it wouldn’t load. I know that I tried that, because I could see warnings about an incorrect version whilst watching Safari start up on the console. The fix is quite simple: change the MaxBundleVersion in the ist file from what it was, to 5528.16. Thanks to Sylvain Frébourg, MiddleClickClose is now working with Safari 4. If you don’t yet have it installed, follow the directions here. If you already have it installed, follow the directions below for changing the version number to 5530.17 and your old installation should work.

#Mysimbl tab download#

I have just updated the plugin distribution, so if you download it now, it should work. Update: Apple released the production version of Safari 4 yesterday at WWDC.

#Mysimbl tab update#

Update: It should now work with all future versions of Safari without having to update it again. If you already have it installed, you can just edit the ist file that will be in ~/Library/Application Support/SIMBL/Plugins/MiddleClickClose.bundle/Contents, removing the two lines that look like this MaxBundleVersion If you re-download and re-install, you shouldn’t ever need to update it again. This is, after all, a dirty hack, so why not make it even hackier? I’ve decided to stop that and have removed the MaxBundleVersion from the ist. I usually play catch-up with Apple and get MiddleClickClose updated a day or two after a new Safari ships. The problem is that every time Safari gets updated, Apple increments that number and SIMBL won’t load the extension any more, since it proclaims that the maximum version of Safari it should be loaded with is the previous version. From what I read about SIMBL, good practices said that you should include a key called MaxBundleVersion whose value was the internal version number of the app you were patching. The problem lies in the file ist that is part of the plugin. Yesterday Apple release Safari 4.0.3 which, of course, broke MiddleClickClose. Update: For Snow Leopard compatibility, see here. MiddleClickClose Updated For Future Safari Versions If not, your only option is to run Safari in 32-bit mode. The SIMBL developer has said that he only has a PPC machine running Tiger, so I don’t really see how he’s going to get it running. The solution is, most likely, to get a 64-bit build of SIMBL, but I don’t know if that’s a simple matter or not. If SIMBL won’t load, neither will MiddleClickClose.

MiddleClickClose is totally dependent on SIMBL.

Once you do that, SIMBL and MiddleClickClose both load, and the plugin works. It is possible to get it working again by right-clicking (or whatever the native OSX clicks are to get the context menu) on the Safari program in /Applications, selecting Get Info, and then checking the “Open in 32-bit mode” checkbox. I had already heard from someone that this was so, and I had expected it, so this was no surprise.

#Mysimbl tab mac#

I have upgraded my Mac to Snow Leopard, and as soon as I loaded Safari, I could see that MiddleClickClose was no longer working. We are very thankful for the dedication of this community and everyone creating and sharing their campaigns, units, and battles and hope to see and play even more going forward.Update: MiddleClickClose has been updated for 64-bit Safari. Because of your endless creativity, you and other players will never run out of new units to try or campaigns to beat.Īnd with the next updates to the game, we know that you’ll make even cooler stuff! One of the reasons we included the Unit Creator in the game is so that you and other players can keep innovating and creating awesome campaigns and units. Recently TABS reached over 1,5 Million units, campaigns, and factions in the workshop! WOW! It just isn’t possible to work on new features for the game. This made us reevaluate most of our future updates like the Hero Unit and additional features to the UC. It can take the designers a day of crashes to even load into the project, and once they make changes it’s super common for other things to break and create more bugs. Secondly, due to TABS having been developed for over five years, it’s at a point where it is super hard to work in.