Good job. Yes, if the Target.IsValid API is not going to work for me in the False condition, then I'll probably have to use this Auxillary approach and have to change all of my Offset and Profile test condition statements in the nested IF functions of all my Expressions.
I imagine the Warnings are simply indicating that the Target is not being found?
Ok. ANOTHER Epiphany!
I've found a way to make it so that I don't even need the OA.
I need curb on the left and right side from 0+00 to 0+40. So I had created offset alignments from to and from the appropriate stations at 7.5ft left and right. Then I had my SA searching for these OAs as a way to decide whether or not to show the curbs.
I found a nifty little thing that I can use in a decision called Baseline.Station. If that number is Equal to 0 OR 40 or if that number is BETWEEN those two values, it draws the curb. NO OA NEEDED. YIPPEE
EDIT: Here's what the flowchart looks like.
I received this confirmation of the OffsetTarget.IsValid (Offset Target Class) defect. I am using the workaround you suggested, just slightly modified to use one Auxillarry Point to test for movement to provide a True/False Decision making capability.
We are using this in our custom ditch subassembly. This workaround won't have the same performance as the API function.
Is there any futher update on this issue? I have the same problem with a stripping subassembly I have created. I'm not sure the work arounds discussed here will work for me.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.