HI Every one,
I am using "FeatureByPositionReverse" to get the feature which have to be the one after original point.
But I am not very sure the index of the original feature is "15". after traversing the feature tree, I found there are a few hidden thing before original point.
if it is a fixex index of every SW part, then I can easily lock the target .
pls help to advise.
regards
Vincent
Hi,
I guess getting first feature after Origin is bit tricky because it may vary based on your modelling. Other way you can get the required feature is to traverse feature tree with ModelDoc.FirstFeature
Logic should be like:
Feat = Modeldoc.FirstFeature
While Not Feat Is Nothing
If Feat.GetTypeName = "OriginProfileFeature" then
Feat=Feat.GetNextFeature
Exit While
End If
Feat = Feat.GetNextFeature
End While
Feat will be your required feature after origin
Hi Taunk,
I have tried this method to get my feature, and it can get my feature any way. However, in an assembly, there are hundreds parts needed to be check the feature that is just after the originie
So if I can get it in straightway without checking others, there will optimize the speed of my macro.
Feature just after the origine, if its index is fixed in part feature tree, I can let that thought done.
regards
Vincent
Vincent,
I always prefer a method which gives me 100% correct result each & every time instead of methods which I am not enough confident, that may give you surprises after sometime which you have not even thought of.
Apart from the solution, for optimizing macro speed you can do some setting before actually starting the traversal.
Use this setting, It will drastically improves macro performance
swApp.UserControl = False
swApp.UserControlBackground = True
swApp.CommandInProgress = True
swModel.FeatureManager.EnableFeatureTree = False
swModel.FeatureManager.EnableFeatureTreeWindow = False
After traversal toggle all settings.
Hi Taunk,
Thanks for the suggestion, it is gonna be helpful to enhance the performance.
regards
Vincent
will this work in C# as well (for add-ins)? That's pretty nifty.
Yes ofcourse, as theses are the Solidworks application's user accessibility settings & graphics property which need not to display during the macro running. Disabling these will speed up the sequence of API call no matter which language you use to write your program.
you can select the feature by name.
public Feature GetFeature(ModelDoc2 model, string fieldName)
{
int featCount = model.GetFeatureCount(); // get a head count of features
Feature feat = (Feature)model.FirstFeature(); // target the first feature
// traverse through each feature in the feature tree in the model document
for (int i = 1; i <= featCount; i++)
{
if (feat.Name == fieldName) // if the feature name is found, return a pointer to the feature
return feat;
feat = feat.GetNextFeature(); // traverse through each feature in the feature tree
}
return null; // feature not found
Looks like it's the 15th index
The 16th index is "tables". Which isn't the first feature
22 seems to be the first feature.
Hi , Dimtry
seems you worked on a assembly doc, you might try on a part doc.
regards
Vincent
I thought that too before I posted, but I get the component earlier. My add-in gets dimensions from a selected component from an assembly. Assembly->get component. Component->get features. I'd have to modify my program to work from within a part document, but it will work the same way.
Note that index 21 is the sketch within the feature (within boss extrude 2). When I try this with a sweep, then the sweep feature would be "22", the sketches would be "21", "20". In your case, since you have an imported part, it would be different, depending on whether you enabled the sketches, the sketch planes, and etc...do you see how it becomes a problem when you have different features directly after the origin? I'd have make a new add-in and see if I can directly grab the first feature without traversal
Or rather: assembly->get selection->convert selection to component->get model doc of component->get features of model
There mother be another way. I'll have to make a partdoc add-in to test it.
Option Explicit
Dim swApp As SldWorks.SldWorks
Dim swMod As SldWorks.ModelDoc2
Dim swAssy As SldWorks.AssemblyDoc
Dim vComponents As Variant
Dim vComponent As Variant
Dim swComp As SldWorks.Component2
Dim swFeat As SldWorks.Feature
Sub main()
Set swApp = Application.SldWorks
Set swMod = swApp.ActiveDoc
Set swAssy = swMod
vComponents = swAssy.GetComponents(True)
For Each vComponent In vComponents
Set swComp = vComponent
Set swFeat = swComp.FeatureByName("Origin")
Set swFeat = swFeat.GetNextFeature
Debug.Print swFeat.Name
Next
End Sub
I think he wants the very first feature after the origin. It's tricky. Here's why:
if the first feature has multiple sub features, then the main feature is stored after all of the sub features. You'll have to know how many sub-features a feature has. If the imported part is complex and has a lot of bodies/surfaces, the main feature index could be quite a ways down the list.
Hi , from your screen capture, it seeems the index of origin is always "14" , a fixed number...ha ha seems it work for me.
regards
Vincent
I think he wants the very first feature after the origin. It's tricky. Here's why:
if the first feature has multiple sub features, then the main feature is stored after all of the sub features. You'll have to know how many sub-features a feature has. If the imported part is complex and has a lot of bodies/surfaces, the main feature index could be quite a ways down the list.