TURLY  Sorry, forgot to update the webpage.

Previous version is available here:

http://www.finderpop.com/FP210.zip

Could you please use the FinderPop Support forum http://www.fnarr.net/fp and detail exactly what doesn't work with FruitMenu?

Thanks!  
(Version 2.1.2)

TURLY  Whoa, some serious anti-APE feelings here and in numerous emails people sent me. To clarify:

FinderPop is COMPLETELY INDEPENDENT of the APE installer. FinderPop does not install APE. The APE control panel is completely unaware of FinderPop's existence, and vice-versa.

What happens is that FinderPop now uses the same code as APE to "patch" the system calls which allow FinderPop to do its stuff. This APE patching code is tiny, less than 0.1% of FinderPop code, has not changed since 2003, and has not caused a crash since then. Unsanity supply a small object file containing this patching code. Because it's better than the patching code I was using previously, I use it. It is more flexible, uses less memory, and (obviously) is compatible with other Unsanity products, should the user happen to be using any. This was not the case previously - if the user was running FinderPop and a haxie that happened to "patch" the same things simultaneously, it often resulted in a crash. No longer.

If there's a FinderPop-related crash, the bug will be in MY code, not the 150-odd lines of "APE" code that actually does the patching.

I think all the bad press that APE gets is not APE's fault per se, but bugs in various haxies (possibly including Unsanity's own, it has to be said.)

Please let me know if that doesn't explain things or if you have information which contradicts any of the above, which is my understanding.

Thanks, and

Have Fun!

--turly  
(Version 2.1.2)

TURLY  Hi, those Cocoa crashes have been fixed in the latest beta - see http://www.fnarr.net/fp/viewtopic.php?t=51  
(Version 2.1)

TURLY  See http://www.fnarr.net/twp

It's still not ready for release on MacUpdate...  
(Version 2.0.1)