Before I create a SR with that Bug, I ask if it's a feature, which I can anywhere deactivate!? ...
And after the re-select in Schematic, the checkbox is still checked!!! We think it's a new bug, or????
as work around ... by script you can still disable it
Okay... I did it.....
before running my script...
after running ...
Okay. I attach my script for free, if anyone need it.
If your link-symbol-names are not beginning with "link", you must correct the sourceline 37.
Best Regards, Juergen Hinterleitner.
Do you experience problems of displaying label by script as discribed in this SR #3195745261 ?
I don't know #3195745261 (access), but I think I know what you mean... if you do the command: "ObjectLabel.Visible = true/false" --> that does not work in the GUI. although the visibility-Checkbox after that action has the correct state!
And that's why I use instead (also in the script above)... "ObjectLabel.Visible = 0/1". That works also in the GUI .
the SR now has a DR linked.
DR/ER #: 01345613
thanks for the tips....it works. How did you discover that ?
just in any sample script at any time. Sry, have forgotten where. But it works
--> The integer for True = (-1), and False = (0). But the Mentors CheckBoxes States works with (1/on) and (0/off). That's why.
Juergen,
Thank you so much. We are about to update and I am glad to know about this ahead of time.
From my experience Mentor needs to step up its Quality assurance. I have found so many defects (8 pending defects at present and I think number 9 is coming soon). Many of them just using basic tool features.
To clarify, the defects I have found are in version 2.3
This is a known defect. From Mentor support.
"Yes, there was a change in behavior that started making the visibility of the net
name enabled automatically. I have linked your service request with DR 1235452 which describes this issue."
"Please take a look in Setup > Settings > Advanced. See if you have the “Automatically synchronize link and net names” setting enabled. If so, this will cause the net name to always be displayed. Try disabling this setting and
then try unchecking the net name box to confirm if this allows it to turn off the net name display."
Well if you disable that, then the link won't have any name.
We still want the link to inherit the net name, but the net itself don't show label (too many label)
up to 2.3, we can still manually disable name of net connecting to link, but in 2.4 ..it's not possible, other than by script ..!!!!
The DR is, I believe that , if the net having net name invisible, adding a link should not change the existing visibility of the net (i.e make it visible) because the link already have the net name.
Have the same problem and I opened a Service request, answer is:
The setting 'Automatically synchronize links and net names' no longer allows the net name display to be disabled.
Come on Mentor why you always disable or change options and make it worse?
We want the option to get the old style like in VX.2.3 back! Now we have to make scripts to solve this?
I call this a bug!!!!
Don`t change options like this and work on functions that over years and year don't work.(PADS Settings Migration.......)
Give us an explanation why you changed this!!!!!!!!!!
We are aware of this and working to fix it in a forthcoming release.
Hopefully nothing else get broken ....
I appreciate the heads up on this. We have not yet upgraded to 2.4
Juergen,
We want to update also but may hold off. Which 8 or 9 defects do you have or know about?
Then need to have more beta testing. Last time I remember them asking for beta volunteers was VX.1.2.
Hi,
what defects you have found?
Mentor needs a very longer testing and a testing of normal users!!
The guys that change things normally don't work with the programs!
from our finding, specifically to 2.4, those below are so critical that they are now in pending release
symbol editor crash on changing grid to 0.02
plane is affected elsewhere when resize plane
pin mapper does not add pin information
Thanks, is it possible that you can say more about "plane is affected elsewhere when resize plane" I can' open this site.
(The other 2 are critical too, but I don't design in 0.02 grid + don't need the pin mapper(don't even know what it is ))
We do not design in 0.02 grid neither but if by accident you change your grid to that value, symbol editor will crash.
Pin mapper is in library manager, when you want to create part with fracture symbol
#01350363
this one you have to keep your 2.3 handy ... and use library manager of 2.3 (lucky that they are compatible !!!)
PADSPro: Moving vertices of plane shape creates bad angle, incorrect outline. Regression compared with VX.2.3
#01351707
this one have some work around
This is not yet fixed in VX2.5 !!!!!
The just started working on it now.
Hmm, the status says "resolved , fixed" .. I would expect it is resolved and fixed and that date march 12 ...not start working to fix it ... well ...
I can confirm... not resolved in VX.2.5 - Update1.
They just started to work on it on 3-12.
exceptions prove the rule, but when it takes as long as other things, then we'll get it in yeeears at the earliest... (2.9 or 3.3) - that just had to be now.
The DR states 'Fixed' because it is fixed for VX.2.6 and is currently in the process for being back fitted to VX.2.4 and VX.2.5. It will be announced in update releases for VX.2.4 and VX.2.5 when the process is complete. We cannot say which updates it will be in at this time.
Is PADS Standard Plus also affected? I am not able to reproduce the issue on our VX.2.5.
maybe not, PADS std+ use different code I beleive.
Only Xpedition and PADS professional are using same piece of code ...
PADS Std+ is also affected, all of the flows use the same code base.
Thanks for precision.
I did not expect that long to fix something that is working well before and just broken at 2.4 (it's not a new feature ...)
if it's taken that long then .... looks like they implement something else ... ...wait and see . hopefully there's nothing else broken after it's fixed
This was introduced after we added the ability to automatically synchronize links and net names which was a new feature in VX.2.4, unfortunately with an unforseen consequence.
Thats not true, this was also available a few versions before VX.2.4!!
You are correct, my mistake, though the regression was introduced due to some related changes around this functionality, the details of which I don't recall.
adding to s.kofler answer "it works perfectly in VX.2.3". I wonder why mentor make change (and what are changes ) and then break it ... and now it will take 2 major releases to bring it back to where it works before ... I'm very curious ...
There were changes made to support pass-thru pins that lead to this. And no it won't take two major releases, you will get a fix in an update.
Well you could already fix it in VX.2.4, now we have VX.2.5 and it will be fixed for version VX.2.6.
Even if we get now a fix in VX.2.4 and VX.2.5 there at least we wait 1 major release for a "little" problem. You could have fixed it for VX.2.5
Mentor needs to understand that we Designer need this little funktions more then big new funktions!
I don't understand why you can't fix this little problems faster.
@s.kofler: my words. Also I can't believe, the ultra bad bug with the mentors own scripting editor - highlighting bug.
I'm not sure, For a long time ago (I think it was in 2.1) it worked very well. In each following Release, the highlight is dead. Mentor fights vehemently against to fix this, since a lot of Major Releases... no highlighting anymore.
btw, there's has been 5 updates for VX.2.4 ...
Hi Robert
have you any idea which update will it be ?
since we always have a problem of compatibility even between update
Release update should be compatible
we prefer to make only one upgrade per release. We will wait until the good release to make transition to VX.2.5
Yes, if update are compatible, users can quickly make transition to new update.
Another Problem with the Updates is that you always have to change all configurations on every PC!!
Altium does it better: There is a unified Settings Menu for all, Schematic, Layout etc. You can export the Settings and import it on other PCs.
Even on update you can migrate fast all settings.
In PADS you have to change every single file on every PC (powerpcb.ini; Filters/Workspace in the Designer, Color Settings for Layout/Router.....)
That really sucks.
Altium is in that miles better!!!!
A lot (all) works in Altium more intuitive. I know that
Well Altium is more intuitive, but with all that freedom you have its easier to make errors.
The reaseon why we don't change to Altium are:
Pads Router is much more powerful then Altium (Altium is unusable to route, modify traces).
Altium has a horrible bus design in schematic.
......
I also do not like the fact that updates wipe out all the configurations on every PC. I created an Idea about it. I spent a long time trying to straighten it out in an SR and finally gave up.
Have a way to store settings so they can be shared between users and restored after update
Take a look and vote
maybe we should wait until VX.2.6
why wait?
Robert said: "The DR states 'Fixed' because it is fixed for VX.2.6 and is currently in the process for being back fitted to VX.2.4 and VX.2.5. It will be announced in update releases for VX.2.4 and VX.2.5 when the process is complete."
then we will wait for 2.5 update ...to avoid all the headaches of compatibility, even among updates of same release !!!!
If updates are compatible between them (as other tools/verndor) then we can afford to update everytime it comes out ...
The release notes provided with an update will tell you if the update is compatible with previous versions and whether you need to update all products at the same time.
I think you understood it wrong Robert.
We want that Version VX.2.3, VX.2.4,VX.2.5..... etc are compatible.
For example Altium, there I can open a File with a lot of versions of Altium
When I open a Schematic in PADS with VX.2.4, then I can't open it anymore with previous versions!
Different conversation and our software is only fowards comaptible, this has been the case ever since the software adopted the iCDB database, in the case of the Xpedition flow since 2007 and PADS a little later. This will not change.
Hi Rob,
There are two approaches taken by companies:
Historically companies have offered a way to convert the design into a previous version for the need of opening a design in an older tool.
IF not then an extra effort was made to allow to open documents as long as possible without needing to upgrade.
Examples of the first approach can be found in Cadence "downrev" tool. It converts the design in a way that it makes it possible to open the design in a previous version of the tool. It is clearly stated that functionalities that where introduced in the newer tools may be lost when converting back to previous revision, but 90% of the time the whole project is read ok.
Example of the second approach can be seen with Microsoft Word, where you can still read and write old documents made and edited across a wide variety of versions. No need to check the version of your Word program to see if you can read it. And no need to ask anybody to which version of the tool they have to make sure that they are capable of reading the document.
I has been suggested many times through different ideas that Mentor would also make such a tool, but for whatever reason, Mentor insists on not offering this option. Compared to other companies it make Mentor look unprofessional and at times very arrogant in the chosen approach.
Multiply this with layout tools, simulation tools, verification tools, data storage tools, tool for manufacturing, PLM tools, mechanical tool and you may start to feel the problems. They are not minor problems, they are huge problems.
I feel the problems of phiet , s.kofler and all of the other tool user (including our site), and I wish this would be addresssed by Mentor.
This discussion started with a simple error in the tool. It has expanded to this topic, and could branch in any direction, when you start to mix bugs, bug fixing time, tool releases versions, hot fixes, tool file compatibility, and so on.
That my 0.02[any currency]
Matija
phiet just an info: I have reported meanwhile 3 more bugs since 2.4 or 2.5 ...
a) in layout you set the option "do not open 3d view after reopen", and you close the Layout with the 3D View as the last active window. Now, start the designer and open the layout via the red layout-button. the layout window is not maximized. (#3307074441)
b) designer crashes when you try to delete (mostly single-selected) link-symbols. but not when you disable the option: "sync link-labels with net-names" (#3307053171) fixed in 2.6
c) drawing editor shows wrong layers for all boards on all sheets, except for the activesheet. after you re-generate the variant data, and update then the DWG. (#3308852971)
There is now an official Article....
https://support.mentor.com/en/knowledge-base/MG603970
This means it will not get fixed fast??
It's completely insane as solution ... I don't know who wrote that note but ...that defeat the purpose ..
uncheck that box mean ...the link will not have name .. user will have to manually input the name to the link AND disable the name ...
better off to use the simple script ...
It does say to only turn it off temporarily. Make the nets not visible and then turn them back on. Assuming it works then it is a work around, albeit a painful one.
"Workaround is to temporarily turn off this check box in Setup > Settings > Advanced > Automatically synchronize Links and net names and afterwards those netnames on wires can be turned of via Properties dialog. Then the above mentioned checkbox can be toggled back on once net names on the nets are made invisible in the properties dialog."
I hope it is true that it will be fixed in 2.6.
I have never understood when a user would want the links and net names not the same. I instruct all our users to turn auto-synchronize on, otherwise we end up fixing mismatch issues. I would love to see a use case for turning it off. Someone at Mentor must think it is a good idea since it the default setting is turned off. I would like to see automatic synchronization set by default
please try it yourself and you will see how ridiculous it is
- take 4 clicks to go to Setup > Settings > Advanced > Automatically synchronize Links and net names to uncheck the box.
- click ok/apply (5th click)
- add a link => no name on the link. you will have to manually enter the name or
the note say you can check the box .... (another 4 click to check the box)
- if you turn the net name off just before, then the link will not have the name. You you don't , then link will have same name but back to start line: ..you can not turn off the signal net name anymore !!!
It's more funny if you add link by copying existing link nearby by Ctrl + LM click .... I think you can see the problem ...
And now all thoses operation EVERYTIME you add a link ..I think you just slow down yourself by more than 500%.
We instruct our user to add all the links on the page, at the end they just 2 click or (get a shortcut key) to run the script to hide netname for whole page ...
(May I suggest Mentor simply integrate that vbs script to the software )
We are due to deliver a patch to address this as indicated before. It has taken longer than we would have liked but it is imminent.
Hi Robert,
When you say "patch" is that something we can use immediately or do we have to wait until 2.6?
Thanks
It will be in one of the bi-monthly updates that come out and you install over the top of your current version. They are cummulative, so if you install update 4 over update 1 it includes the items from upates 2 and 3.
This is now available as a fix in VX.2.4 Update 11
Any data for PADS Std+ fix?
In the works, I don't know which update yet.
There is only VX.2.4 Update 5????
Update 11???
Yes, Update 11. The update for VX.2.5 is also in the works and will be in update 5.
Why isn't it in the todays released Update-4 (VX2.5), but in the for 5 days released Update for VX2.4?
It is a matter of resources to build and test the fix in each version and flow.
There is no Update 11!!
The most actual is Update 5
Update 11 is for Xpedition flow, PADS will follow, when I know the update number I will update this thread.
Ours go up to 11.
SpinalTap.
I guess the way I would do it.
1. Draw the schematic pages with the automatic synchronization turned on. I NEVER work on a schematic with automatic synchronization turned off.
2. Turn off the auto-synchronization
3. select all nets going to the off pages on a page by page basis.
4. hide the names by unchecking the box in the properties
5. Turn the auto-synchronization back on.
I am not saying I like it, but if you do not want to run a script then it will work.
Yeah thats als my workaround, but I don't understand because Mentor can not patch this little option fast. They invent functions that nobody uses, but can't fix this little option!!
Please vote for my new Idea too. Thanks
Add a possibility to import constraints from Excel to the constraint manager (DesignRules)
I submitted an idea to have the automatically synchronize links and net names turned on by default. If you agree then give it a vote!
Here it is
automatically synchronize links and net names should be on by default
Cheers!
For us PADS STD people!
Hello:
The solution for the below Defect Report / Enhancement Request (DR/ER) is currently planned for delivery in Release PADS VX.2.6. The Planned Release is subject to change.
Service Request (SR) #: 3208376971
SR Description: Unable to hide "Name" on Nets
DR/ER #: 01235452
DR/ER Description: Automatically synchronize link and net name changes the net name visibility
DR/ER Status: Validated
DR/ER Resolution: Fixed
DR/ER Customer Note: Assigned. In Engineering WIP- Software investigation taking place.
Planned Release: PADS VX.2.6
As I posted earlier in the thread, updates are in the process of being rolled out for PADS as well, just to be clear:
Xpedition VX.2.4 (already done) & VX.2.5
PADS Pro VX.2.4 & VX.2.5
PADS VX.2.4 & VX.2.5
When I know the numbers I will update this thread. The reason for your message on the SR is because we make the fix in the current engineering release and then port that back if/as necessary. Not all fixes get ported back unless deemed significant enough to need a patch.
Finally Update 5 for EEVX2.5 is out:
https://support.mentor.com/en/product/852852130/downloads
Thanks to Mentor for finally patching this bug.
BTW: in Update 5 for EEVX2.5 this is the only fixed item in DxDesigner. (Sad, as there is so much known stuff to correct, and EEVX2.6 so far away)
Cool..
But at this rate, we will all be retired before seeing all fixes requested, let alone enhancements ...
I agree. I have several logged defects that are still being reviewed to see IF they will be fixed. There are requests that are accepted but are over 5 years old and have yet to be scheduled. This is not encouraging to the users who have to work around the problems every day.
now I understand why many veterans stop reporting bugs ... people would rather find work around themself ... that's sad
It's also sad that with each new upgrade, new (endless) bugs arise.
As with the DrawingEditor, which destroys (since 2.5) all views of the contained sheets, every time after the Pcb has been saved (or the FXE data was recreated). Mentor acknowledged this new bug, but with the hint, that it will not be fixed in 2.6, and will not be reviewed until the end of the year!
Mentor has to change his bugfix politics drastically!
What if all clients change to its competitors?
Altium for example tries to fix bugs fast!!
Mentor can only win, but they won't...
Until now no Bugfix for PADS VX.2.4!!!!
That's how people at Mentor work. They prefer to add new features that help to win new customers (more money) than to please their long time users by correcting those little bugs that spoil our daily lives ...
I am one of those users who stopped writing SR for bugs, because it takes forever to get them fixed. It's also the same for new ideas, they are rejected when they feel that it takes too much effort to implement them ... even if some of these ideas could be used to correct issues or poorly implemented features in their tools.
it's frustrating considering that we (like other users) took time to make snapshot, record video, prepare testcase (as we don't want to send real design out everytime... to demonstrate beyond any reasonable doubt that it's a real bug and a fix is needed ... on the other hand Mentor wonder why tool like Altium becomes more popular ...
They simply know that changing to a competitor will most of the times not come into question because it's too expensive for the employer. Well, most of the times is not never
I'm on PADS pro 2.4. We use same workflow (i.e enable link name, and disable net-name)
I confirm that I cannot hide name of net connecting to the link anymore. There's will be too many label.
Lucky that I only do some test with 2.4..not moving everyone to 2.4 yet...we will stay on 2.3 for now...since there's too many problem with 2.4 for us.