MILKE  Thanks for the comments. I'll try to address some of your complains...

- Contextual menu entries... You may be right, but (not being a native English speaker) I really didn't manage to come up with something better, even though I tried. I may very try to find someone to do a proper English localisation, since all wording is done by me and I'm perfectly aware that's not an ideal solution. But you've just given me an idea, perhaps it's much better to use "Create ZIP..." for commands that ask some questions (parameters settings) before acting and to use just "Create ZIP" (no periods) for commands acting immediately.

- Springy not appearing in the contextual menu... You can find more explanations of this behaviour on the following pages:

http://www.springyarchiver.com/support/topic/topic/50

http://www.springyarchiver.com/support/topic/topic/55

To make the long story short: if you set Springy to show up in the "More" submenu, it will always be there for you. But if you set it to show in the root of the Finder contextual menu, every time you reboot, or logout/login, or change Springy settings from "Show in "More" submenu" to "Show in the root of the menu", the first time you show contextual menu you won't see Springy in there (in the root) and you'll have to disclose the "More" submenu (Springy won't be in there either) once. Only after that procedure, Springy will always appear in the root of the menu. I repeat, you need to disclose "More" ONLY ONCE after reboot, logout/login or setting change. This is the consequence of trying to put Springy in the root of the menu and I hope it's a small price to pay for people that want it there (in the root), which eventually makes navigation much quicker.   
(Version 1.5.5)

MILKE  Starting from version 1.5.5, there is an option in the General preferences panel to show Springy in either root of the Finder contextual menu, or in the “More” submenu like Apple intended.  
(Version 1.5.5)

MILKE  I really apologise for the inconvenience, but you should've just sent a message to support address once your license became invalid. And off course you weren't supposed to pay twice. Once again I apologise, but changing licensing model was necessary. I didn't want to rely on Kagi license system any more since it's quite easy to break and to generate fake license codes. That's what the new license is all about. It was introduced with the version 1.5 of Springy on April 1, 2009 (when it changed its main icon as well).

I have sent new licenses to all existing users (prior version 1.5) at that time, including you, and I didn't see it bounced back to me as undelivered. I suspect that you didn't receive it for some reason. Perhaps it ended in your spam box. I've just checked your profile here on MacUpdate and I see no purchase with your name, so you probably haven't used it at the time. Please send me an e-mail to license@springyarchiver.com with you old registration data (e-mail address you've used to register will suffice) and I'll sent you the new license. Whether you still like Springy and plan to use it or not, you've paid for it and you're still entitled for it.  
(Version 1.6.1)

DEVSH0P  I have to be fair, so I'm making an additional comment on this.

It hasn't been 2 hours and the issue is resolved. I wasn't expecting it, and didn't ask for it, but to the developers credit, this is far and away the fastest support to an issue I've ever gotten. 5 star support service without a doubt.

And for anyone that wants to make a stink, it was a complicated issue that couldn't be resolved through normal channels up front. But I must say, the dev has gone above & beyond to make things right.

Thanks again man, I appreciate the commitment to your work.  
(Version 1.6.1)

LITTLEB  Answer to the question here

http://www.springyarchiver.com/blog/topic/116  
(Version 1.5.4)

SHOCK J  Ok, scratch my comment. It just "magically" appeared. Very strange. There is a bug/issue though. I use Path Finder primarily. Path Finder has the option of "appending the Finder's contextual menu items" in "a Submenu" or at "the End" of Path Finder's CM. Springy only shows up in Path Finder's CM if it is set to "at End." If it's set to "a submenu" you get nada. Personally I do prefer Springy at the root level, but it would be great if I didn't have to have ALL the Finder CM items at the root level.

I would love for Springy to play a bit nicer with Path Finder's CM. It has always been a bit "off." For example, it seems that the font size for Springy CM is hard coded. Path Finder has the option for a "small contextual menu font size." When this is checked, all the other 3rd party CM items font sizes adjust down appropriately, but Springy does not. So all the other CM items are at 9px, where as the Springy CM item is still at 12px. Just looks weird.

These are minor gripes. At least it's working for me now.  
(Version 1.5)

ANONYMOUS  Unfortunately, Springy menu not appearing when you choose to show 3rd party CMs in a submenu in Path Finder contextual menu is a consequence of the way SpringyCM now works, all that in order to put it into the root of Finder contextual menu, which was request from many users (I still hope Apple will come to it senses and bring 3rd party CMs back where they belong, in the root of the menu). I'll see if there is anything I can do regarding this.

As of menu font size, no, it's not hard coded in Springy, it's just default, 12pt. If the official CM plug-in interface is used, menu items are inserted as AppleEvent record and list objects. A real creation of menu items is done by the system and in such case it eventually creates menus with fonts of correct size. In order to put Springy in the root of the contextual menu, I don't implement that interface fully, but I insert menu items directly, using appropriate Menus API. When specifying menu item text, and if font size is not specified, it just defaults to 12pt. This is easy to fix, and I'll do it in 1.5.1 or 1.5.2 most probably.

The biggest problem with SpingyCM 1.5 and Path Finder is something you didn't even mention: SpringyCM 1.5 is hardy functional with Path Finder! Again, this is due to the workaround in order to bring Springy back into the root of the contextual menu. SpringyCM is displayed in Path Finder, but when you click some Springy command, some other Path Finder command is called instead. I tried really hard to debug it and find out that like Path Finder is "eating" so-called "command event", so SpringyCM doesn't see it at all. I am in contact with Path Finder author and I'll see what I can do to fix this one, which is a real show stopper for SpringyCM in Path Finder.  
(Version 1.5)

DARYLF2  Please PLEASE offer an option for the old Springy contextual menu, the one that appears in the More submenu. I've had a ton of problem with contextual menus, ranging from slowdowns to Finder crashes. After a lot of troubleshooting, I narrowed it down to the new Springy contextual menu plugin. Removing the new Springy plugin got rid of the Finder issues. The old Springy plugin always worked fine.

I really used the Springy contextual menu a lot, though, so not having any Springy contextual menu makes the software far less useful to me.  
(Version 1.5.1)

MILKE  @SHOCK J

Springy CM plug-in is now (almost) fully functional when working with Path Finder! The only thing which wonÂ’t work is extracting particular file from an archive while browsing through hierarchical contextual menu. Namely, browsing is still possible, but clicking on a menu item representing a file in the archive will NOT work. This functionality has to be implemented using Carbon command event and that event cannot be caught in a Cocoa application, such Path Finder is. By the way, this particular functionality has never worked, I hadnÂ’t even known until IÂ’ve tried it recently (I'm not a regular Path Finder user).

DARYLF2

Finder slowdowns and crashes were not related to Springy CM not being in the "More" submenu, but due to some other problems and errors in implementation, which were corrected in version 1.5.2. Anyway, starting from version 1.5.5, there is an option in the General preferences panel to show Springy in either root of the Finder contextual menu, or in the “More” submenu like Apple intended.  
(Version 1.5.5)

MILKE  I'm very sorry for the inconvenience you have with Springy. I guess you experience crashes in Safari and Mail the moment you try to show some contextual menu in those applications, right? The problem is caused by the Sparkle framework, or better said the modifications I've done to it, used to check updates. Since it's meant to be included in applications only (not in plug-ins, such are SpringyCM), I modified it and used some tricks to load it into the plug-in. Seems that wasn't such a smart idea after all :-(

The workaround for this problem is fairly simple and so far it worked with everyone having the same problem: remove SpringyCM from the contextual menu items folder and then install (copy) it again from the Springy disk image you've downloaded. Logout and log back in and the problem should disappear. If it's still there, please let me know. Even better, send a crash report to support@springyarchiver.com

For the version 1.4, I prepare the complete redesign of Sparkle framework for the SpringyCM. It won't be included in the plug-in as a framework, but will become an integral part of it. That way, the problems like and similar to one you have will be gone.  
(Version 1.3.3)

DOCEATMAC  OK, it seems to work, no further Safari or Mail crashes till now. Thank you very much for the immediate help. Great support!  
(Version 1.3.3)

MILKE  It will be fixed in version 1.3.3. Unfortunately, Leopard brought some more quirks to both application and CM plug-in (some of them are bugs in Leopard in my opinion) and I expect to have them fixed by the end of this week. As of the feature you mention, I'm still investigating, but I'm almost sure there will be no other solution than to move the root menu item of archive contents (the one titled with archive name) one level deeper into menu hierarchy, hence in Springy submenu, where all other Springy commands are located. The way Leopard works with third party CM plug-ins is completely changed, plug-ins are not being even initalised before "More" menu item in the root of the Finder CM is highlighted. That prevents me to catch the moment when that submenu is populated so I can change the name of the menu item and attach archive contents hierarchy to it.  
(Version 1.3.2)