I have created a project on Google Code for the custom context-menu.
http://code.google.com/p/custom-context-menu/
I have copied all the comments from my original posting over to the issues tab, uploaded the code, made a few wiki entries and such. This is the first time I’ve ever used Google Code so please feel free to make any improvements to what I’ve started.
There isn’t much that I can do beyond this point other than to ask everyone interested to blog about this so that hopefully some Javascript experts can jump on this and get this working reliably.
I’m going to look into creating an interactive chart that we might be able to use to track testing. Hopefully I’ll be adding a custom right-click to the charting app real soon. :-)
Please add me to the project on the Google Code, I have made a fully working version (IE7, FF2, Safari) and would like to share the code
Post + link to demo:
http://www.uza.lt/blog/2007/08/solved-right-click-in-as3/
@Paulius, Awesome work. I added you as a project owner at Google Code.
I just thought that leaving myself as the owner and adding others as members was a little degrading. The community owns this now.
@CISNKY, thanks for passing this along on your blog.
great work by you… thanks a lot..
the code what u gave for the external interface calls error in flash can u explain how to apply this code of action script to call the external interface?
I was hoping Adobe would have thought about the ability for developpers to change the vanilla contextual menu in removing/adding elements. ( …How a naive dude I am ! :D )
This work-around might perhaps need some tweak because of the external-interface use (I am not yet familiar with this concept -your JS code will be a superb helpful for a first training- but I guess there must be some situations making the whole thing harder than if a more basic AS3 listener had been possible, am I wrong ?)
Whatever, very nice job, and it allows a lot more than a simple plugin mode to the vanilla Adobe right-click contextual menu would have add : Many thanks to polyGeek and CISNKY for sharing their work about this ! :)
@FR_dZastreux, there are many instances where the ExternalInterface just breaks down. It’s rare but the things that can break it are so varied that it’s impossible to test for everything. And if so then this whole workaround collapses. The reason Adobe doesn’t give developers complete access to easily replace the context-menu is for security. Yeah, I don’t buy it much myself. But that’s their stated reason.
And I can’t take credit for any of the cool JS. That’s all CISNKY and Uza’s handy work.