1 of 1 people found this helpful
I see there is an issue DR/ER #: 01352342 with control of unused pads. See here for discussion. Yahoo! Groups
I am having issue with the New search window not highlighting/selecting items in the search window when selecting. UPDATE2((There is an attribute "ComponentTracking in the dbc that now controls cross probing. In VX.2 it had no effect.
There is also the hide nets issue.Unable to hide "Name" on Nets since VX.2.4
Same question here. We are with VX 2.2 too.
1) Is VX2.4 a stable release? The last thing we want to do is to upgrade to a version that will have to be upgraded again soon, because we have a whole team using the same version. It is just not worth the time doing it.
2) Me experience shows once a PADS Designer VX 2.2 project is opened by VX 2.4, it will no longer be opened by VX 2.2. Can someone confirm the backward compatibility?
I have never known DxD to be backwards compatible, I believe since ViewDraw when it got it start. As soon as you open a design in a newer version you can't go back. Version control comes in really handy to recover from that.
I first checked out ViewDraw in 1993 or 1994 and thought it was pretty cutting edge at the time... I can't believe DxD still looks and operates the same way.
That's not my recollection. ViewDraw used to be ASCII text files under the SCH directory, and those loaded fine for me on newer or older versions of ViewDraw. Then ViewDraw became eProduct Designer and later DxDesigner, and I was still able to load newer ASCII-file schematics in the older versions of the tool.
When DxDesigner became an encrypted binary database, then I believe backwards compatibility was lost.
Correct, once a project is opened by VX.2.3 or later, then you cannot open it in VX.2.2.
even updates are not backward compatible ...
if you have 2.3 update 10, someone else that have 2.3 no update cannot even open it..it's insane .. and update can be rolled out often (up to 20+ ) for a version ...so we decide to not doing update ...unless the particular update fix a show stopper bug
we moved to 2.4 ..and they have introduced some annoyed bug ... I don't think there will be any version without bug so we just live with it and find some work around ... that' why automation is very handy
2.5 is out now to fix some reported bug... and I'm expecting some other new bugs ... at different places ...
Agree with hitec100 on when back compatibility changed, however would have to say when I was learning Viewdraw back around that time frame I wouldn't agree it was cutting edge, I sat in the training class with numerous disruptions from people complaining about
not being backwards compatible to the very first piece of code ever written for this product. Teacher finally had to say no more or your out.
My take away from class, tool was still archaic still did not have quite a few features and functions numerous other tools had.
Probably because had to stay backwards compatible to day one code.
I would think it's pretty hard to develop cutting edge new features when your hands are tied like that.
But some other tools do allow saving to much much older versions but of course you lose any features the old tool didn't have.
Thanks. I am shocked that backward compatibility is not even possible for the updates. With new updates being rolled out from month to month, I have no confidence at any new VX or updates until they would call it final.
Does anyone know if the licensing has changed for the PADS DxDesigner/Logic to PADS Layout flow VX.2.4 ?
We are still on VX.1.0 with Mobile Compute(Node-Locked) and Network/Floating licencing configured.
I heard the "Node Locked" may have been removed...is that correct?
No, that is not correct -- node-locked licenses are still supported.