ilogic create custom ipropertie
Accepted solution
Where are you going to put the iLogic rule to create the custom iProperty? Will you put it in the Content Center part or in the assembly? If it's in the assembly, how will it find the Content Center part and when will the rule run?
Here's some code to create a custom iProperty in a part, if it is not found:
Dim propertyName As String = "MyProperty"
Dim propertyValue as String = "Test Value"
customPropertySet = ThisDoc.Document.PropertySets.Item("Inventor User Defined Properties")
Try
prop = customPropertySet.Item(propertyName)
Catch
' Assume error means not found
customPropertySet.Add("", propertyName)
End Try
iProperties.Value("Custom", propertyName) = propertyValue
Mike Deck
Software Developer
Autodesk, Inc.
Here's something along the same lines too. It's a bit lengthy, but good information.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @jpi656UL. If it is possible to set-up that way, it would have to include some 'triggers' that would automatically run the rule again every time the active sheet changes, to keep the property's value up to date. Currently there is only one event listed in the 'Event Triggers' dialog which has anything to do with drawings specifically, and that is 'Drawing View Change' (uses the OnViewUpdate event), which only gets triggered when something in the model changed, causing the view to be updated to match the model. So that trigger won't work for this situation. You would need to create a custom event handler code to be able to trigger this rule to run every time the active sheet changes. The only other drawing specific event I can think of that has an event handler code established for it is the 'OnRetrieveDimensions', which is obviously not what we want here. So, I'm not sure any code exists to handle the event we want to monitor here.
But here would be one possible representation of the iLogic rule for creating/updating a custom iProperty that records the name (or number) of the active sheet. Then some code to place the title block with that value in its first prompted entry value.
Dim oDDoc As DrawingDocument = ThisDrawing.Document
Dim oSheet As Sheet = oDDoc.ActiveSheet
Dim oCProps As PropertySet = oDDoc.PropertySets.Item(4)
Dim oNameProp, oNumProp As Inventor.Property
Try
oNameProp = oCProps.Item("ActiveSheetName")
oNameProp.Value = oSheet.Name
Catch
oNameProp = oCProps.Add(oSheet.Name, "ActiveSheetName")
End Try
'Try
' oNumProp = oCProps.Item("ActiveSheetNumber")
'Catch
' oNumProp = oCProps.Add(0, "ActiveSheetNumber")
'End Try
'For i As Integer = 1 To oDDoc.Sheets.Count
' If oDDoc.Sheets.Item(i) Is oSheet Then
' oNumProp.Value = i
' End If
'Next
Dim oTBDef As TitleBlockDefinition = oDDoc.TitleBlockDefinitions.Item("TitleBlockDefName")
Dim oPromptStrings() As String = {oNameProp.Value}
oSheet.AddTitleBlock(oTBDef, TitleBlockLocationEnum.kBottomRightPosition, oPromptStrings)If this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click (LIKE or KUDOS) 👍.
If you want and have time, I would appreciate your Vote(s) for My IDEAS 💡or you can Explore My CONTRIBUTIONS
Wesley Crihfield
(Not an Autodesk Employee)
Hi @planner_mobbs_engineering. Quite simply, the value data Type of a custom iProperty is set by the Type of data you set at its value. Because of this, you can actually change a custom iProperty's value type by simply setting a different type of value to it. For instance, any value you give to it that is within quotation marks will be understood as text (String), and therefore will set its data type to text. If you set an unquoted numerical value to it, which has decimal places, it will be understood as number (Double) by default. If you set an unquoted numerical value to it, which has no decimal places, it will be understood as number (Integer). If it is formatted as a Date, it will be recognized as Date. If you set either True or False as its value, it will be recognized as 'Yes or No' (Boolean).
However, standard (not custom), pre-existing iProperties can NOT have their value data type changed this way. And many of the standard ones are also ReadOnly, instead of Read/Write.
Wesley Crihfield
(Not an Autodesk Employee)