iFeature Inputs in API Empty

[Anonymous]

I'm doing some operations where it would be really useful (essential except that I've made a work around) to be able to access an iFeature's inputs, but they're empty in the API. I'm just wondering why this isn't supported? It doesn't seem like it should be difficult to store and expose the reference object, given that they should all be supported objects such as planes and points.

 

kelly.young has embedded your image for clarity.

[BrianEkins]

The inputs are supposed to be empty because the iFeatureDefinition object represents the iFeature that will be created and you need to define the entities that will act as inputs for the iFeature to use when creating the result. 

You can see an example of this in the help sample:

http://help.autodesk.com/view/INVNTOR/2018/ENU/?guid=GUID-8E822596-71C5-4C93-B935-7A6F04C7DE10

[Anonymous]

Thanks for your response, Brian. I'm talking about an ifeature which is already defined, ie. the inputs have aleady been given. My ifeatures have been placed using a couple objects, including a sketchpoint. I'm trying to find that sketchpoint through the ifeature object. In that case, should the inputs still be empty? Is there somewhere else that I'm missing to look for the existing inputs?

[BrianEkins]

Sorry, I misunderstood.  I would expect the behavior you're looking for.  It seems to me like the current behavior is a bug.  I looked back through my earlier programs because it seems like I must have used this at some point but I wasn't able to find an example program so I can't be sure this has ever worked, but I would assume it has in the past.

[Anonymous]

I've been doing this for 3 years and can say  I haven't seen that work in that time. I also came across a forum from 2003 where someone complained about this, so I think it's a continuous issue. Thank you for confirming that you don't have any alternate use cases!