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?
You could use dbCreateVia and do it yourself...
There's a lot of complexity in the via form - particularly because of populating with relevant information from constraints and so on. So if you use dbCreateVia then you have to do a lot of the work yourself - the form takes care of providing higher level functionality. If you want access to some of that higher level functionality without the form, I'd suggest you contact customer support and ask for an enhancement to give what you want, such as maybe an leCreateVia function to correspond to leHiCreateVia.
In reply to Andrew Beckett:
Thanks for the inputs, Andrew.
Preparing to write an auto via placer using dbCreateVia, I've been looking at the via stacks that get placed with leHiCreateVia->Auto (or Stack). The routine places an instance of each via in the stack according to the definition from the techfile. The interesting thing is that the vias are attached to eachother. If you select one you select the entire stack. But I cannot see the connection mechanism in the db properties. In the past I've used a parent/child attachement method. But the parent/child nodes for these stacked vias are nil. How is the attachement being made?
In reply to Michael Robinson:
In reply to skillUser:
In fact, selection of stacked vias reacts to the FULL and PARTIAL switch in a vertical sense. When the FULL switch is on, all the vias get selected, only one gets selected when the PARTIAL switch is on. I betcha we three and programmer are the only ones that know this.
Well now I can't duplicate what I saw the other day. With the Via Stack option selected, I was able to select one or all of a stacked via by toggling the FULL or PARTIAL select. What happened?
Yes. I was probably moving too fast and fooled myself into believing I saw a cool feature.
Speaking of, wouldn't that be a cool feature, vertical partial/full select for via stacks?
Ahhh, but my way doesn't require an extra button. Cadence's course of fatter GUI's is a hindrance. Via stack partial/full select could have been included with the regular partial/full selectability and doubled the efficiency.
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...
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.
In reply to dmay:
Setting the values into the current window property is subtelty I've not seen before.