Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Unwanted update when using Feature Group

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

If you use the Feature.MakeCurrentFeature method in NXOpen API and you use make current feature interactively, it should behave the same, if not, I would report it as a bug.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Unwanted update when using Feature Group

Gears Phenom Gears Phenom
Gears Phenom

How are you adding the features to the FeatureGroup?

If you use the addMembersWithRelocation() method and supply true for either of the boolean parameters, you are saying to NX it is OK to move and/or update features:

void addMembersWithRelocation(Feature[] members,
                            boolean reorderTimestamp,
                            boolean updateRelocatedFeatures)
                              throws NXException,
                                     RemoteException
Adds given features into feature group.
License requirements: solid_modeling ("SOLIDS MODELING")

Created in NX8.5.1

Parameters:

members - Features array

reorderTimestamp - Allow reorder member features in order to make members sequential

updateRelocatedFeatures - Allow update features when members are made sequential

Graham Inchley Snr R&D Engineer (Systems Development), Sandvik Coromant
Lenovo ThinkPad W540, Win7, 16GB. Developing in: Java | C | KF
Production: [NX8.5.3.3 MP11 64bit] Testing: [NX12.0.2 MP1]

Re: Unwanted update when using Feature Group

Solution Partner Legend Solution Partner Legend
Solution Partner Legend

I am making feature group active and then do tim and unite. Trim and unite operations go into feature group as it is supposed to be, but each operation causes update of features down the tree  - or at least down the features that are added by my code. This is not the case when I simply add trim and unite features at the end of the feature tree without ising feature group.

Re: Unwanted update when using Feature Group

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Is it a timestamped or floating feature group?

 

Can you post your code? Without it, we are essentially just guessing.

Re: Unwanted update when using Feature Group

Solution Partner Legend Solution Partner Legend
Solution Partner Legend

Timestamped group.

 

Can't post right now, because I'm currently working on other parts of it, and section to do with feature group is currently not present there. I'll try to post something, but it will be later.

Re: Unwanted update when using Feature Group

Solution Partner Legend Solution Partner Legend
Solution Partner Legend

After careful line-by-line investigation, I have found where my problem was. The trick was to make feature group active and make current the one before it. This way everything runs smoothly.