It's a round-about way to do it.
Each net has segments. Each segment can have a label. The label is what you see as the net name. So for each net, you have to get the segments, iterate through them, see if each has a label, and if so, make the label invisible.
I thought about that too, but that will explose the runtime ...
I guess there's no better way to do it
A shortcut does exist. For a given Net object, the Label object is returned by Net.GetConnectedLabel(Net.GetSegments().Item(1)). But, if you label multiple connected segments of a net with the netname, you will need to use the longer method.
I will start with that and if anything left, will do it manually after...
I had forgotten about that one.
I also have great admiration and respect for your contributions to the Mentor user communities.
In case you have not seen my latest posting on the Ideas Xpedition page, I invite you to check it out:
I have more of a 'deal with it, this is the way it's going to be' mentality about such defects, and I do my best to work around them. A large part of my automation work has been done to replace existing functionality that either doesn't work or doesn't work very well. RF ground vias, placement of XREFS, and Replace Part (granted this one has been fixed in the VX.2.2 release, but come on, that took a while) come immediately to mind.
The way I see it, the core functionality of Xpedition is very good. The failings are opportunities for me to do it better. It has been made clear many times that what drives the Mentor engineering team are a very complicated set of directives that often make no sense to us, the users. I don't pretend to know what they are or how they are prioritized, so I pick my battles and move on the best way I can.
I agree with Patrick that we have no choice but to patch it for our need ..however, I also feel disappointed that we have to patch an expensive software for very basic feature that all many lower end competitor already support to enhance productivity ...
Actually all those little thing that slow people down ....because people have to find a work around and ...frustrated ...
I like the fact that I can throw an idea at Patrick and a few days later he has a solution. I am so spoiled
So, regarding your initial desire to hide all net names: In VX.2.2, Mentor introduced Display Control for xDX Designer (Introducing the Display Control ), which can be opened from the View pulldown menu. On the Objects tab, in the Text section, the Names item (which is equivalent to Labels) can be toggled on or off. Names, or labels, can only be added to components, net segments, and pins. Unfortunately, Mentor did not provide these three subcategories under Names in Display Control, so when Names are toggled off, component names, nets names, and pin names all disappear, without any user automation. So, adding these subcategories to Display Control should be the basis for a new Mentor Idea.
This is certainly a nice idea. I will certainly vote for your idea
However, in my original case, I want net name to be off so I can selectively turn them on later.. in such case toggle off by display control is not my option.