Stats

  • Locked Locked
  • Replies 13
  • Subscribers 143
  • Views 18275
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using the code the GUI uses

Michael Robinson

Cadence GUI's are bulky and clunky. I want to drive the behind-the-scenes code that Cadence GUI's drive.

For example, le0ViaForm. I can set the variables that are used in the form: le0ViaForm->viaMode->value="Stack" from skill.

But those variables don't exist until the form is called at least once. So the first time my skill is run, it errors.

Once the form has been initialized (manually), using the form variables is difficult because of Cadence's 'unreal time' timing.

Yes, I know about hiRegTimer. That's a kludge.

Driving the inputs to a GUI from Skill is like yelling at a driver on the freeway going 70mph to change lanes. 

How can I access to the real code behind the GUI's? Where is the reference to the code behind the GUI's?

  •  I respectfully disagree. They're different operations. I can see cases where you might want to select a section of a track, and the entire via stack at the end of that segment.

    Since it's an icon on the screen, or a bindkey, it's not exactly a "fat" GUI...

    Still, everyone is entitled to their view point! Some customers wanted these to be separate - they can't be both separate and combined...

    Andrew.

  • Cadence's flexibility with Skill code makes this so you can have it if you want it by creating your own bindkey:

     geTogglePartialSelect() hiGetCurrentWindow()~>viaStackSelection = !hiGetCurrentWindow()~>partialSelect

    Put this on your F4 bindkey and you get what you want. If I don't want it I don't have to add it.

    Derek

  •  Derek,

     

    Well done.

    Setting the values into the current window property is subtelty I've not seen before.

     

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.