Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I have created a form that has a cyclic list a radio button (or boolean, it doesn't matter) and several float fields.
For instance I have
var1 float_field11 float field12
var2 float_field21 float field22
I would like to
1) change the editable property of each float_fieldx1 depending on the value of the cyclic list
2) change the editable property of each float_fieldx2 depending on the value of the corresponding float_fieldx1 and the value of the radio button (all disable if radio os on "Off" position.
I managed to implement 1) but I'm having trouble in getting 2) to work.
As of now I'm using two different callbacks for the cyclic fields and the radio button.
It lookd like my code works fine when the cyclic list has few elements, however, when the list grows up it doesn't refresh the fields anymore.
Any help is very appreciated.
The code appeared to have a couple of (what I assume were) mistakes. In the function exUpdateFloatFields it seemed to be leaving the cyc11stFloatField enabled when cyc3 and cyc4 were chosen - which I assume was not what you wanted. I've modifed that and uploaded - but I'm not sure if that was what you were complaining about?You could almost certainly write the code to figure out the field names to enable/disable from the cyclic value, which would avoid the big case statement, but I don't think that's what you were asking - I'm assuming you're expecting just one of the four sets of float fields to be enabled at once - if so, that was the coding error which I corrected in the attachment.Andrew.
thanks for your reply. However, I put multiple activation at once on purpose. I now solved the issue by using hiUpdateFormBlock(form) inside the exUpdateFormFields. I found that in the regular documentation.