Unable to Select and Unsuppress Center of Mass Feature

[loeb]

When I insert a Center of Mass feature, it ends up being suppressed in all the unactive configurations even though I have the "Suppress Feature" setting unchecked in the properties for every configuration. So, I wrote a macro that will iterate through every configuration and every feature, looking for a feature of type "CenterOfMass", then unsuppress it. The problem is that my SelectByID2 statement is returning FALSE. Here's a code snipit. Thanks for your help.

Code: Select all

    While Not swFeat Is Nothing
        If swFeat.GetTypeName = "CenterOfMass" Then
            BoolStatus = swModelDocExt.SelectByID2(swFeat.Name, swFeat.GetTypeName, 0, 0, 0, False, 0, Nothing, 0)
            BoolStatus = swModel.EditUnsuppress2()
        End If
        Set swFeat = swFeat.GetNextFeature
    Wend

[acmall]

To give you another option you can select the Center of Mass in the Feature Tree then go to Edit - Unsuppress - All configurations

I did a quick check in SW2022 SP5.0 and I am not seeing the Center of Mass being suppressed in the non active configurations.

[gupta9665]

Try this

BoolStatus = swModelDocExt.SelectByID2(swFeat.Name, ucase(swFeat.GetTypeName), 0, 0, 0, False, 0, Nothing, 0)

[josh]

Don't use SelectByID2. SelectByID is what the macro recorder uses, but it's almost always the wrong thing to use when you're actually writing a macro. In this case, you already have a pointer to the Feature object, which has a Select2 method.

But, in fact, since you already have a pointer to the Feature object, just use the SetSuppression method of the feature. Selecting it is a waste of time because SW will take the time to update the graphics etc to show the selection.

In fact, if you use SetSuppression2 method, you can unsuppress in all configurations at once without having to cycle through.

[AlexLachance]

To give you another option you can select the Center of Mass in the Feature Tree then go to Edit - Unsuppress - All configurations

I did a quick check in SW2022 SP5.0 and I am not seeing the Center of Mass being suppressed in the non active configurations.

He is looking to do it through API.

[loeb]

Try this

UCASE? That's nuts when swFeat.GetTypeName literally returns "CenterOfMass"

Thanks

[loeb]

Don't use SelectByID2. SelectByID is what the macro recorder uses, but it's almost always the wrong thing to use when you're actually writing a macro. In this case, you already have a pointer to the Feature object, which has a Select2 method.

But, in fact, since you already have a pointer to the Feature object, just use the SetSuppression method of the feature. Selecting it is a waste of time because SW will take the time to update the graphics etc to show the selection.

In fact, if you use SetSuppression2 method, you can unsuppress in all configurations at once without having to cycle through.

Thanks, Josh. That works. When I find a feature of the right type, I use
BoolStatus = swFeat.SetSuppression2(swUnSuppressFeature, swAllConfiguration, Nothing)
to unsuppress it in every config all at once.

Now my problem is that this only works for preexisting COM and COMRP features. If I try to do it immediately after creating a COM or COMRP, using
Set COM = swModel.FeatureManager.InsertCenterOfMass
or
COMRP = swModel.FeatureManager.InsertCenterOfMassReferencePoint
they remain suppressed in every other configuration, even after unsuppressing them like you suggested.

I even tried rebuilding after inserting the features, but before unsuppressing them with no luck using:
BoolStatus = swModelDocExt.Rebuild(swRebuildOptions_e.swRebuildAll)

[gupta9665]

UCASE? That's nuts when swFeat.GetTypeName literally returns "CenterOfMass"

Thanks

Yes because recorder was spiting "CenterOfMass" as "CENTEROFMASS".

[loeb]

Yes because recorder was spiting "CenterOfMass" as "CENTEROFMASS".

I don't use the macro recorder. When I use print.debug to print the type, it was in mixed case..

[gupta9665]

I don't use the macro recorder. When I use print.debug to print the type, it was in mixed case..

That is correct and that is how I started to check. But when it did not worked, then I use the recorder and then found the mystery of upper case.

[acmall]

He is looking to do it through API.

Point taken!

When I read the original post I was not sure if the API route was being taken because he was not aware there is a built in option to unsuppress features in all configurations hence the suggestion. If he already knew about this well and good but I think it is always good to make sure.