that file is how we do it. you just have to be clever with your overriding. it's possible to structure it so that you can still access the default behaviors, but by assigning them different names -- like MayaOpen, MayaSaveAs, etc -- and keeping the default names -- Open, SaveAs, etc -- for your own custom stuff. for example, we override pretty much everything, but our gui that overrides "SaveAs" has a "free-style" button (with an icon of snoop dogg) that brings up the normal maya save gui via "MayaSaveAs" in pv_performAction. does that make sense? i'm just rattling this off...
-chad -- http://groups.google.com/group/python_inside_maya To unsubscribe, reply using "remove me" as the subject.
