Is there anything in the API that lets me access a feature being "adaptive"?

[chris]

Example, if a feature is adaptive I'd like to have an if/this assigned to it to perform some math, however if it's not adaptive it would perform different math. I'm currently handling this with a custom parameter called "Adaptive", but it involves a manual step and I'd rather iLogic just handle it automatically.

Basically I'd like to have something that looks like this:

If Feature.IsActive("Beam Profile") Is Adaptive Then
Parameter("d51") = (d45)
Parameter("d52") = (d45 / 2)
Else If Feature.IsActive("Beam Profile") Is Not Adaptive Then
Parameter("d45") = B_L
Parameter("d51") = (B_L)
Parameter("d52") = (B_L/2)
End If

[chris]

This is what chat gtp gave me, but I don't need the code to search the entire part, I already know what specific feature would have it or not, so would there be an easier way to write it as a "true/false" if the specific feature is known? 

' Get the part document
Dim oDoc As PartDocument
oDoc = ThisApplication.ActiveDocument

' Get the part component definition
Dim oCompDef As PartComponentDefinition
oCompDef = oDoc.ComponentDefinition

' Loop through all features in the part
Dim oFeature As Object
For Each oFeature In oCompDef.Features

' Check if the feature is adaptive
If oFeature.Adaptive Then
' Output the feature name and its adaptive status
MessageBox.Show(oFeature.Name & " is adaptive.", "Adaptive Feature Found")
End If

Next

[chris]

I was also given this code, but iLogic said that "let" and "set" were no longer supported? 

' Get the part document
Dim oDoc As PartDocument
oDoc = ThisApplication.ActiveDocument

' Get the part component definition
Dim oCompDef As PartComponentDefinition
oCompDef = oDoc.ComponentDefinition

' Specify the name of the feature you want to check
Dim featureName As String
featureName = "YourFeatureNameHere" ' Replace with the actual feature name

' Find the feature by name
Dim oFeature As Object
On Error Resume Next
Set oFeature = oCompDef.Features.Item(featureName)
On Error GoTo 0

' Check if the feature exists
If Not oFeature Is Nothing Then
' Check if the feature is adaptive
If oFeature.Adaptive Then
MessageBox.Show(featureName & " is adaptive.", "Adaptive Feature Check")
Else
MessageBox.Show(featureName & " is not adaptive.", "Adaptive Feature Check")
End If
Else
MessageBox.Show("Feature " & featureName & " not found.", "Error")
End If

[Curtis_Waguespack]

@chris , try this syntax

If Feature.InventorFeature("Beam Profile").Adaptive = True Then
	MsgBox("Adaptive")
Else
	MsgBox("not Adaptive")
End If

[WCrihfield]

Hi @chris.  Those AI bots usually get things mixed up, like mixing VBA keywords into iLogic rules.  It does not understand the iLogic API system that well either.  Maybe try this way of formatting the iLogic rule.  It uses Inventor API way of accessing the features, but uses iLogic API for working with the parameters.

Sub Main
	Dim oDoc As Document = ThisDoc.Document
	If (Not TypeOf oDoc Is AssemblyDocument) AndAlso (Not TypeOf oDoc Is PartDocument) Then Return
	Dim oFeats = oDoc.ComponentDefinition.Features 'Type varies between assembly and part
	If oFeats Is Nothing OrElse oFeats.Count = 0 Then Return
	For Each oFeat As PartFeature In oFeats
		If oFeat.Name = "Beam Profile" Then
			If oFeat.Adaptive Then
				Parameter("d51") = d45
				Parameter("d52") = (d45 / 2)
			Else
				Parameter("d45") = B_L
				Parameter("d51") = B_L
				Parameter("d52") = (B_L / 2)
			End If
		ElseIf oFeat.Name = "OtherFeatureName" Then
			If oFeat.Adaptive Then
				'Parameter("X") = X
				'Parameter("X") = (X / 2)
			Else
				'Parameter("X") = X
				'Parameter("X") = X
				'Parameter("X") = (X / 2)
			End If
		End If
	Next oFeat
End Sub

If this solved your problem, or answered your question, please click ACCEPT SOLUTION .
Or, if this helped you, please click (LIKE or KUDOS) 👍.

[chris]

@WCrihfield Thank you for the help, can you please give me an explanation of the segments of the above code? I get the red section, as it's pretty much my existing rule, but what is the blue section saying and what is the green section for? 

[chris]

I have a variant of what I want to happen working from the simple message box that @Curtis_Waguespack added, but while it will change from adaptive, it will not change back without manually running the rule. What the rule is trying to be is this:

when I place a template of the structural member, I have a parameter that allows the user to define the length they desire, however, which of course carries with it a way to show a total length in the parts list. (that being the "B_L". However, if the user decides they want to use "adaptive" to stretch that part between other parts, then they can do so, in which case I need "d51"-end plane  and  "d52"-mid plane to follow whatever the adaptive length now is. But if they decide they don't want to be adaptive, then those dims need to fall back to it's start stage, that is being based off the "B_L".

I have this working fine with a custom parameter called adaptive, but it causes problems if the user forgets to check it before they change the feature to adaptive.

The actual geometric length is being handled with this for the parts list:

Geo_Length = Measure.PreciseExtentsHeight
iLogicVb.UpdateWhenDone = True
InventorVb.DocumentUpdate()

[WCrihfield]

The blue section...

I was not sure if you were working within a part or assembly, but I knew it had to be either one or the other, but that this rule should never be ran on DrawingDocument or PresentationDocument, so I used a simple filter to eliminate that possibility.  I like to use the 'TypeOf' operator these days, due to it simply seeming to process faster than using the Document.DocumentType & DocumentTypeEnum check.  Then, I already know (from experience) that the AssemblyComponentDefinition.Features property returns the 'Features' Type, while the PartComponentDefinition.Features property returns the 'PartFeatures' Type, so I did not specify the Type of the collection object being in Line 4, because the Type varies.  Then, since I did not 'declare' the Type of that variable, I needed to first make sure it was not Nothing, before checking its Count, just as added error proofing.  When using a For Each...Next type loop, if the collection object is Null (such as no value assigned to that variable), that will throw an error, but if the Count of the collection is zero, that is OK (no error), it will just not do anything.

The green section...

I just assumed that you may have more than one feature that you wanted to control the same way, so just showing an 'ElseIf' section for filling that part in, if needed, but was not really necessary.

I posted that last example before seeing what Curtis posted.  His example does certainly look a lot more simple, because it takes advantage of that iLogic API method.  Pretty much anything that can be done with iLogic API can be done with Inventor API, but using Inventor API usually involves more code.  There are definitely pros & cons for going either way with the code.

[Curtis_Waguespack]

@chris , I don't know of anyway to catch the event with iLogic, that occurs when the adaptivity is toggled .

maybe someone else can think of something?

[chris]

@Curtis_Waguespack can you show me how to get the code to auto update as soon I change the feature to not adaptive, currently it requires me to manually run the rule? (not sure why there is no thumbnail)

[WCrihfield]

Nothing comes to mind for me either.  I looked into ModelingEvents.OnFeatureChange Event too, but not useful in this case.  It does get triggered, but the event does not provide any useful information that could be used for this case, because 'Context' is empty.  We would have access to the Document and the Feature, but without 'Context' help, we would have to 'test' if the 'Adaptive' is different during the 'kBefore' vs 'kAfter' timing, using one or two a share variables.  Might be possible to use that way though, but I have not done enough testing.

[chris]

Okay, thank you all for your help, I'll just have to make sure to manually run that run

[Curtis_Waguespack]

@chris, if I understand correctly, I would likely wire up that adaptive checkbox in the form to trigger the rule in the part, so that it sets the adaptivity and changes the parameter logic also.

see the form and rule in the attached example part model using the code below

Feature.InventorFeature("Beam Profile").Adaptive = isAdaptive

If isAdaptive = True Then
	MsgBox("Feature is adaptive, params = d45")
'	Parameter("d51") = d45
'	Parameter("d52") = (d45 / 2)
Else
	MsgBox("Feature is NOT adaptive, params = B_L")
'	Parameter("d45") = B_L
'	Parameter("d51") = B_L
'	Parameter("d52") = (B_L / 2)
End If

[chris]

@Curtis_Waguespack  @WCrihfield  How about this, would I be able to make the feature adaptive with a true/false checkbox, so that I wouldn't have to also go RMC the feature?

[WCrihfield]

I think I found a way do to this using that Event I mentioned (ModelingEvents.OnFeatureChange ).  It was just slightly more complicated than I had in mind.  I created an iLogic rule example, just for testing purposes, and it seems to be working just as planned so far in my testing.  That Event is for every model document, across the whole application, the entire time Inventor is running, so I had to come up with a way to limit that to only focusing on one document, and only while that one document is open, then get rid of itself when that one document closed.  So, this example includes 2 ways to get rid of the EventHandlers after they have been launched.  One way is using an iLogic SharedVariable, where I can change the value of that from another rule, then run the original rule again which senses the changed value, then removes them.  I have been using that method for years.  The other one is subscribing to the DocumentEvents.OnClose event for that specific document.  And when that event happens, it gets rid of the event mentioned above, and eliminates the OnClose one because the document is no longer available.

Next, I had to declare several variables between the routines, so that they would be held in memory while the EventHandlers were still running, and could hold on to a value between the 'before' & 'after' timing of the event, so that they could be compared to each other.  Since this event gives us a reference to both the document and the feature, I first check if the document matches the one we want to monitor, and if not, it does not respond.  Next it records the Feature.Adaptive status to those variables during both before and after timing, then compares the variables values during after timing to see if they are different.  Then the code only responds when they are different.  Then it just collects data from the 'Context' (none in this specific case) and writes a report about this event and the status change to the iLogic Log window.  The whole part where it checks Context and writes a Logger report out could be replaced with a call to run an iLogic rule instead, or just put some simple code in there to do a task like what you are trying to do above.

The test code example is attached as a text file, because it is rather long.  I did include a lot of comments in there, and left some of my other Logger statements in there, but commented out.  You can get rid of those to reduce code size and clutter.  If you have questions, feel free to ask them.  

[WCrihfield]

Any checkbox you put into an iLogic Form would have to be backed by a UserParameter with Boolean units.  So back to what Curtis suggested as far as that goes.