Annotation Browser, QT form?

Hi All,

When using the Annotation Browser for Incomplete Nets is there away to
get the list of incomplete nets in SKILL(from the browser)?
In the old form is was easier(or seems so far)

Something like
IncompleteNetsForm~>theList~>choices would give you the listbox list

IncompleteNetsForm~>theList~>value returns users selections

With the new forms are there equivalent ways to get the data?

_vbAssistantReplay_treeEvent(dwindow('annotationBrowser5) "selection =
0") sets the form to "Incomplete nets" value

_vbAssistantReplay_treeEvent(dwindow('annotationBrowser5) "selection =
0:0") sets to first value in the tree info, how could user do it by
name of net?

For example from above
IncompleteNetsForm~>theList~>value = "vreg"

Thank you,
Eric

 

(setof m cv->markers (equal m->tool "VLS Connectivity"))

should give you the list of all open and short. You may further analyse
the markers.

There is cross navigation between the annotation browser and the navigator,
you can probably get what you want that way.

Yours,

 

I hadn't thought of getting the list from the database that way, that
is a cool way.

Are you saying that the form~>handle~>value,etc, has no equivalent on
the new forms?

As far as using Navigator, I think you are saying I could get the list
of opens directly from the
database and...

_treeNavSelect(dwindow('treeAssistant5) "/MYNET Net")
I am not sure what is going on with "dwindow" and treeAssistant and
the number. For window, there can
be more than one window type? For treeAssistant there can be more
than one?

That is too bad that there is no handle for the user, if that is the
case. I always enjoyed the simplicity of it all.


Thank you,
Eric

 

Jean-Marc Bourguet wrote, on 10/01/10 17:19:

And you can use the hsm* functions to get the selections from the navigator...

Regards,

Andrew.

 

No, I just don't know if there is an equivalent (documented or not). The
annotation browser is an uniform access for all sort of annotation and the
result of the extractor is just one kind of them.

The underscore is a sure sign that this is not documented. I'd not use
that. As Andrew completed, there is a bunch of documented functions
(starting with hsm as prefix) to access and modify the navigator selection.

We have probably lost some simplicity there, but on the other hand the
system is more scalable and probably easier to use after the learning
period.

BTW, you could look if there are documented functions starting with ab*,
that is probably the prefix which is used for the annotation browser.

Yours,

 

Virtouso is IC6.1* has some great new functionality and the look and
feel(tool tips and such) is a big improvement(I was expecting more
functions but assume they are in route?), the losses are less than the
gain for sure and I am sure can be done one way or another.

I could only find hsmDeselect, hsmGetSelectedSet and hsmSelect in the
finder. Are these the functions Andrew was referring to?

I could not find any 'ab' functions.

Are there any functions or ways to write SKILL to perform a flyline
between a known open in the database? Is there an equivalent
to geMakeProbeWithColor for a known open, if you will. If not can I
as a request from my company ask Cadence to provide one?
(Probably can ask, just like I could ask for a big raise from my
Boss .

Thank you for your help and patience,
Eric

 

So there is probably no public skill interace.

I'm not sure I understand what you want. What doesn't dbCreateMaker and
dbCreateLine (on an hilite layer for instance) do which you need? (Your
marker will be available in the annotation browser btw)

Asking is always possible. It may even have an influence on what will be
available. Now, you are starting to use 6.1.4, we are finishing 6.1.5; so
if there isn't a big incentive to modify the current plan, waiting is
probably in order.

Yours,

 

It seems you are saying that there is more changes and perhaps
functions coming in the next release that may give the ability to do
my specific task.
I will wait it out.

Thank you,
Eric

 

I think you misunderstood (i.e. I'm not aware of anything specific to what
you are asking; and for the flyline, I'm don't even know what you want more
than what is available). I'm saying that enhancement requests can take a
long time to get to you: the next release is already in beta,..

Yours,

 

Yes, I did misunderstand.

There is a function to do probes in skill, why not for opens?

I wrote:
"Are there any functions or ways to write SKILL to perform a flyline
between a known open in the database(or I suppose if it is not open it
returns nil)?
Is there an equivalent to geMakeProbeWithColor for a known open, if
you will. "

Sorry for not unclear.

Look forward to the new release regardless.

Thanks,
Eric

 

Yes, I did misunderstand.

There is a function to do probes in skill, why not for opens?



I wrote:


"Are there any functions or ways to write SKILL to perform a flyline
between a known open in the database(or I suppose if it is not open
it
returns nil)?
Is there an equivalent to geMakeProbeWithColor for a known open, if
you will. "

Sorry for not being clear enough.

Look forward to the new release regardless.

Thanks,
Eric

 

Probe is a way of hilighting objects, we don't have objects for opens.

The nearest we have is the markers. The extractor creates markers for
short it find.

Visibility of markers is controlled both by the marker visibility setting
in the LSW (objects section) as for most objects, but also by and isVisible
property on the marker. So if you have a marker m, you may have to do

m->isVisible=t

to make it visible even if the markers are visible according to the LSW.
And the extractor creates markers in the unvisible state.

Does that suit your needs?

Yours,

 

PolyPusher wrote, on 10/04/10 16:54:

Eric,

The point is that the annotation browser provides a way of temporarily enabling
the visibility of markers in a controlled fashion - it's a tool for displaying
markers.

If you've enabled the new layer palette (CDS_USE_PALETTE), you can bring up the
"Guides" assistant and turn on the visibility of markers as a whole. Then if you
find the relevant markers (look at cv~>markers as Jean-Marc suggested earlier)
you can do marker~>isVisible=t and then it will be visible.

This is a bit brute force, and not controlled in the same selective way that the
annotation browser gives you.

So maybe you should contact Cadence customer support and ask for a function to
interface with the annotation browser, which can be given a marker object, and
allow you to specify that you want the annotation browser to display this one.
This would be like toggling the visibility of one of the markers within one of
the categories in the annotation browser. The markers themselves have the
details of the coordinates built-in.

You might also want something to display all the markers associated with a
particular net name, maybe.

So this is all a bit different from probing. You can probe a net - but that will
show the entire net (included the routed parts). Since you you have all these
marker objects, there's much more potential to show more detail.

However, my first question would be - what do you need that the annotation
browser can't already do? What we'd want to try to do is make the annotation
browser the one-stop-shop to control display of marker information - rather than
every customer having to invent their own tool.

Regards,

Andrew.

 

Our team had invented our own tool that performs very specific list of
tasks in IC5X and wanted to support it IC6X, this is not to say it
will be used exclusively. There is a lot of code we will not port
over due to IC6 doing it better or similarly. Everyone I work with is
(well except for a few that are never positive, but please dont get me
started!) very pleased with IC6X so far.

marker~>isVisible=t will be sufficient I think.

Thank you both,
Eric







I think the bruttish method outlined above is acceptable.