Hi folks. This is one for all those heavy mapkey authors out there. We've started looking at moving to Wildfire 2 from 2001 and I'm fiddling with creating a layering mapkey which will be run on all my models. I want said mapkey to automatically put all datum axes on a layer called "DATUM_AXES". This was trivial to do in older pro/e versions, but the complete reworking of the way items are selected to be added to the layer has stumped me. Old mapkeys could basically say #ADD ITEMS; #FEATURE; #ALL OF TYPE; #DATUM AXES;
But, now in Wildfire 2 that functionality has now apparently been finally disabled. I can get the "Search.." tool to locate all the axes in the model just fine, but I'm unable to get a mapkey which will actually SELECT all of them and move them into the list to be added. The mapkey ends up being dependant on the features being named certain names (which I cannot guarantee) in order for them to be selected. There's no SELECT ALL button the way I would expect in the search results area. If I'm working through MANUALLY (not running the mapkey) I can just hit ctrl-a, but I cant find any way of recording that INTO the mapkey.
I can't use "rules" because their are already some features which exist from our starting template parts/assemblies. I can't make a toolkit app because I don't have access to Pro/Toolkit (in my dreams eh?).
This mapkey for adding axes is just ONE part of a higher level mapkey that layers off ALL the features in the model. We want it to continue to be a single push button job that cleans up everything, and very easy for the end users. I'll have to do this same thing with CURVES, PLANES, etc.
I would guess that Jarrod has the same issue we have. Not all features of all models were created with those same settings in the config.pro file. If we use models that came from another source, we need to update them to our scheme. The config.pro options only affect newly created features.
I have created this mapkey (this will first delete all layers):
Hi I do use a default setup for all of my layers in my config.pro and stuff that our group creates is not a problem. My problem comes when I recieve parts from other groups that get incorporated in our products. Prior to wildfire I had a mapkey that worked very well to get everything on the layers I like to see them on. All attempts to create a wildfire enabled mapkey to do this fall short. One mapkey set I had would work fine on the first model and not so well on the second model and downhill from there. If you come up with a solution please post a summary. Thanks Paul