Alrighty! So for anyone else that has this question, I suppose it could be summarized by saying that:
1: Using an external rule (module / function / StraightVB combo) to return normal VB datatypes (integers, strings, longs, etc. etc.) is fine, no matter what your internal rule is doing, so long as the function arguments are also of the normal VB datatypes.
EX: Internal Rule -
AddVbFile "MathMagic.iLogicVb"
Dim Num1, Num2, Num3 As Integer
Num1 = 12
Num2 = 10
Num3 = LargestNumber(Num1, Num2)
Msgbox(Num3)
External Rule (Set to StraightVB Only in options) :
Public Module MathMagic
Public Function LargestNumber(Num1 As Integer, Num2 As Integer) As Integer
If Num1 >= Num2 Then
Return Num1
Else
Return Num2
End If
End Function
End Module Results in a message box that reads : 12
2: Using an external rule (same as above) to return normal VB datatypes, but that require Inventor API specific data types, or that use Inventor API specific objects inside of their block, must be initialized first by making a call to the Inventor API inside of the internal rule that you want the values to be returned to.
EX: Internal Rule -
AddVbFile "MathMagic.iLogicVb"
Dim oDoc As Inventor.Document '<- Inventor API call
Dim oFileName As String
oDoc = ThisApplication.ActiveDocument
oFileName = MyFileName(oDoc)
Msgbox(oFileName)
External Rule (Set to StraightVB Only in options) :
Public Module MathMagic
Public Function MyFileName(SentDoc As Inventor.Document)As String
Return SentDoc.FullFileName
End Function
End Module
Results in a message box that reads : "DriveLetter:\Path\FileName.ipt"
3: Mixing and matching your VB datatype functions with Inventor API based functions will result in bad things happening because occasionally you will need to make a call in a rule that doesn't need to access the API to a function that doesn't use the API. At that point you will receive the problems that I did above, and no one wants you to go through all of that.
EX: Internal Rule -
AddVbFile "MathMagic.iLogicVb"
Dim Num1, Num2, Num3 As Integer
Num1 = 12
Num2 = 10
Num3 = LargestNumber(Num1, Num2)
Msgbox(Num3)
External Rule : (Note the mixing of both types of our previous external rules example)
Public Module MathMagic
Public Function LargestNumber(Num1 As Integer, Num2 As Integer) As Integer
If Num1 >= Num2 Then
Return Num1
Else
Return Num2
End If
End Function
Public Function MyFileName(SentDoc As Inventor.Document)As String
Return SentDoc.FullFileName
End Function
End Module
Results in errors! Because the API was not initialized in the internal rule like it was in Example 2. Even though you don't need it, the external rule does need it despite the fact that you're not even calling on the functions that require it.
Biggest lesson learned? Keep your fancy pants functions that use the API in a separate file than the your mundane typical functions that you'll be using for regular work.
Thanks a lot : to Curtis W for the inital help, and MjDeck who confirmed all things questionable!
--------------------------------------------------------------------------------------
If my solution seems to remedy your problem, please press the Accept Solution button, -
as it increases my power levels and will eventually help to elevate me towards outer space.
Check out my iLogic injection tool here :
http://goo.gl/ce1Qg--------------------------------------------------------------------------------------
