> you just need to stop abusing the global macro feature You put a feature in, you lose control over what people over what people are going to do with it, or expect it to do [;-)]
> It would be quite complicated to determine which macros and their > dependencies are required Fair enough. However, it wouldn't be that hard to create an "Export group" option in the group action menu, would it? And once you've done that, a little tick box for "include global macros" wouldn't be too bad either, I should't think :) Thanks, David Craig <http://www.panix.com/~dac/> ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
