Persistently hide selected PMI in view?

[potrero]

This is probably easy but I can't seem to figure it out:

I've inherited PMI onto a drawing, but I'd like to be able to persistently hide selected view instances of the same type of PMI (for example: I'd like to hide a surface finish annotation in one part of one view). Problem is, as soon as the sheet is updated, the hidden PMI pops back up.

Suggestions?

Thanks.

 

[JohnRBaker]

How did you 'hide' it? Try using Edit -> View -> View Dependent Edit... and 'erase' the unneeded items.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[potrero]

First, I tried right clicking on the specific PMI object and selecting Hide, which does hide the object until the view is updated (at which point the PMI object reappears).

Same behavior when going to Edit>Show and Hide>Hide. Neither of the above two approaches act any differently if the PMI is inherited onto the View only, or onto the Drawing.

John, I tried your suggestion of Edit>View>View Dependent Edit...erase (also tried this by right clicking the view boundary and entering View Dependent Edit that way) but neither approach hides the PMI object.

Still looking for a solution.

BTW the NX version is 5.0.4.1

 

[JohnRBaker]

I personally think the Hide should remain persistent, and I've opened a PR to that effect. If I hear anything, I'll post a status update.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[potrero]

Thank you, John. Looking forward to the fix.

 

[ewh]

I would use visible in view in this instance. I know that many users don't like this command, but I find it very useful. Hide should work, but is to easily changed, since it is all or nothing. I use hide as a temporary tool, and our office standard requires all released files to have no entities hidden. It is just too easy to have a lot of unrelated things hidden, resuting in a mess when someone shows all.

Believe it if you need it or leave it if you dare. - [small]Robert Hunter[/small]

 

[JohnRBaker]

I seriously suggest that you consider changing your standards as Show/Hide is becoming the more preferred scheme for controlling the visibility of objects.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[ewh]

I guess I don't understand how it became preferred. Say you hide something in an assembly drawing, go into the model and work some more, hiding things you don't want to see, then save the file for someone else to work on. They then need to edit the assy further, but need to see the whole thing, so they show all. Chances are good that they are not aware of what has been hidden in the drawing and this introduces the chance of error.
For me it boils down to the fact that it is so easy to show all inadvertently, resulting in wasted time having to go through and re-hide entities.

Believe it if you need it or leave it if you dare. - [small]Robert Hunter[/small]

 

[JohnRBaker]

Another reason one should work with Master Models.

BTW, despite what you may think, layer schemes are not all that common today. In fact, many consider them a holdover from the days of 2D wireframe design and drafting when virtually every single item that you saw on the screen represented a separate independent object such as a line or an arc and therefore with hundreds, if not thousands, of small bits and pieces, we needed some scheme to managed them in a manner where they could be considered part of a single object or class of objects. However those issues are no longer as relevant as they were in the past and so more modern and easier to understand schemes are being utilized whenever possible.

Now this does NOT mean that we're abandoning Layers because we're not (we've even enhanced at least the user interface in NX 6 and plan for more changes in the future), but that doesn't mean that Layers will once again become the primary method for 'cleaning up' your files, but rather just another tool, suitable for some things but not as useful as others.

BTW, I would recommend that you start telling your users to use Edit -> Show and Hide -> Show... INSTEAD of Edit -> Show and Hide -> Show All as their normal means of seeing what else might be part of their model or drawing files. Anyone who would EVER use Edit -> Show and Hide -> Show All on a file in which they do not have a complete understand of is just being reckless as far as I'm concerned.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[MSPBenson]

Maybe I'm showing my age but I think layers could not be efficiently replaced by layers. Some correction on this if I'm wrong would be educational.
Layers are very efficient for grouping relevant construction geometry together. You can label the layer or group of layers to allow subsequent people who develop the part some well needed documentation. Can this be done with show hide?
When dealing with hundreds or even thousands of construction curves datums sheets and sketches to have them all showing on mass is very confusing to the eye and makes selection difficult. Yes users still have to deal with this type of number of construction geometry John.
Being able to switch on/off a group of construction features/geometry is something we could simply not do without.
Am I misssing something here or does show hide have some extra functions I'm not aware of?

NX 4



Mark Benson
Aerodynamic Model Designer

 

[JohnRBaker]

Well as I said, we're not abandoning layers (even enhancing them) for the reasons that you gave, but there are other schemes emerging that will make a layer only approach obsolete. Some of these are things like embedded on the fly sketches and absorbing datums created on the fly by the feature which used them (you'll see more of this last behavior in NX 6). Also there are some objects, like a sketch itself that can only be a single layer and so we're added object groups to the sketcher to collect and manage objects inside of a sketch.

We also have things like feature sets in the Part Navigator since features unless they are standalone objects can't be moved to a layer and in the Assembly Navigator we are using groups there as well which actually behave as filters, which is another type of collector.

That being said layer have several limitations which we would like to think can be overcome in the future. These include the fact that layers have a finite number. They are mutually exclusive (an Item can only be 'on' one layer). They're not hierarchical (I can't add a layer to a layer), etc.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[ewh]

John, is this leading to a "folder" type segregation scheme, where entities can reside in more than one "folder"?

Believe it if you need it or leave it if you dare. - [small]Robert Hunter[/small]

 

[JohnRBaker]

That's what I've been lobbying for. Just create something called a folder where I can describe the rules and perhaps even implement automatic behaviors (like all objects of a certain type, when created are 'added' to this folder). And for old legacy files, we might just create 256 numbered folders.

A folder is just a metaphor and a scheme for presenting it, but in the end it's a 'collector' with certain rules and characteristics as defined by the user, which allows me to perform global tasks/operations on all the members of a folder with a single select operation, such as Hide, Show, Delete, display as 'Red', etc.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[ewh]

Sounds like layers on steroids to me. I'm all for it.

Believe it if you need it or leave it if you dare. - [small]Robert Hunter[/small]