Custom Macro Buttons Unavailable?

I don't know about the button ( I don't think so, though.), but the proper way is to deal with it inside the macro. That way, regardless of whether the macro is run from a button, or by calling from some program, or by the menus, it handles the situation properly. Just have it check the type of document and make decisions/error messages based on that. Let me know if you need an example.

WT

It sure would be nice to have 3 macro toolbars tho woudn't it? One for Assemblies, one for Part files, and one for Drawings. Of course, then I'd probably want one for sketching, and... :)

Ken

well, if you ever write a Solidworks Plugin, you'll find thats

I think it would be a helluva lot easier to just enable/disable a button on a single menu, than having to write 3 (sometimes identical) menus, and let SW display the one depending on what the active doc is.

A quick-and-dirty way around this (if you're running 2001+ or newer) is to just write a single .swp, drop command buttons with images on them, and make the form non-modal. You'll still have a titlebar showing on your 'toolbar', but the form will automatically be on top (no api calls) and you'll have all the flexibility you'll need (for now)

you can create your own toolbars with sldworks::addtoolbar3 you can create your own toolbar command with sldworks::addtoolbarcommand2 you can turn off toolbars with modeldoc2::Toolbars

Now we are headed in the right direction

Well, like I said an add-in will get you closer to what you want but you'll still have to embed all your macros into the add-in DLL. There's no way to invoke a macro via the API.

"Corey Scheich" wrote in news:bhge5v$ftcp$ snipped-for-privacy@ID-200385.news.uni-berlin.de:

you can use FeatureManager::InsertMacroFeature then rebuild. then delete MacroFeature.