How to hide parameters in iFeature insertion dialog

How to hide parameters in iFeature insertion dialog

eddie_kn3
Participant Participant
266 Views
9 Replies
Message 1 of 10

How to hide parameters in iFeature insertion dialog

eddie_kn3
Participant
Participant

Hi,

I’ve created an iFeature for PFC beams that uses a table to drive different sizes (75, 100, 150, etc.).

When I go to insert the iFeature, the dialog box displays every single parameter height, width, thickness, etc. which makes the interface very cluttered. I only want the user to be able to select the "Size" from the table and input the "Length."

I have already tried setting the Length as a custom input and ensuring the other values are not selected as "Keys" in the table, but the dialog still forces me to see and edit every single dimension.

Is there any way to hide these extra parameters from the insertion dialog so only the Size and Length options are visible?

0 Likes
267 Views
9 Replies
Replies (9)
Message 2 of 10

Radwan-Almsora
Explorer
Explorer

To hide those extra parameters during insertion, you need to configure them in the iFeature Author dialog shown in your first screenshot. Currently, those dimensions appear because they are listed in the Size Parameters pane (the top-right window).

0 Likes
Message 3 of 10

eddie_kn3
Participant
Participant

Hi Radwan, thanks for the reply.

I actually tried that exact step by moving those dimensions out of the "Size Parameters" pane and into the "Internal" pane. The problem is that when I do that, the iFeature table breaks. If those parameters aren't in the Size Parameters list, selecting a different size from my table no longer updates the height/width geometry in the part.

Is there a way to keep those dimensions driven by the table so the geometry updates correctly, but hide them from the end-user during insertion? Or does the table strictly require them to remain in the Size Parameters pane?

0 Likes
Message 4 of 10

johnsonshiue
Community Manager
Community Manager

 Hi @eddie_kn3 

 

If a given parameter is configured on the table, it will be shown. I am not aware of a workflow to hide a configured parameter. If the parameter of interest can be driven by an expression, you may not need to add the parameter to the table.

Many thanks!



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 5 of 10

morgann5238
Observer
Observer

I've run into similar situations with iFeatures. Keeping only the essential inputs visible would make the workflow much cleaner.

0 Likes
Message 6 of 10

CGBenner
Community Manager
Community Manager

@morgann5238 

Hi there!  This sounds like a perfect Idea for the Inventor Ideas forum.  Feel free to suggest it there and share what the problem is that this feature or workflow would help solve for you. 

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M


0 Likes
Message 7 of 10

dan_inv09
Advisor
Advisor

In iParts parameters that are not keys do not show up when you are selecting a member - what do the keys do in the iFeature?

[Is this yet another case of Autodesk copying from one interface to another without bringing over the functionality as well? Is this going to be another Ideas post of "Make it work like the other thing that it looks like!"?]

0 Likes
Message 8 of 10

eddie_kn3
Participant
Participant

The catch is that because this is a table-driven iFeature, if I remove those internal parameters during the IDE conversion, I lose the ability to drive them via the Author Table to define the different structural sizes. Inventor forces any parameter tied to the configuration table to appear as a user input on placement, which is exactly why the workflow gets so cluttered. 

0 Likes
Message 9 of 10

eddie_kn3
Participant
Participant

Exactly! In iParts, non-key parameters stay hidden. But in iFeatures, even if you set a primary Key, Inventor still dumps every single size parameter onto the placement screen anyway. It totally defeats the purpose and clutters the whole UI.

0 Likes
Message 10 of 10

johnsonshiue
Community Manager
Community Manager

Hi Dan,

 

I tried creating a simple table-driven iFeature with keys on our internal build. Only key parameters showed up on the placement dialog. Could you share an example that illustrates the inconsistent behavior?

Many thanks!



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes