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????
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.
as work around ... by script you can still disable it
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.
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.
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,
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
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.
Latest info on this:
Fixed
Xpedition
VX.2.4 Update 11
VX.2.5 Update 5
PADS Professional
VX.2.4 Update 9
VX.2.5 Update 5
PADS
VX.2.4 Update 6
VX.2.5 Update 4