• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. asiSelectNet doesn't work!

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 984
  • 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

asiSelectNet doesn't work!

imagesensor123
imagesensor123 over 13 years ago

Hi all,

    have you seen this script in the artist skill user guide, i find it doesn't work in my case. by the way, i use ic5141 and ams370.

this error info:

 Message: *Error* No method supplied for generic function asiGetSimName

 hiCreateStringField(
    ?name ’net1
    ?prompt "Net Name"
    ?value ""
)
hiCreateButton(
    ?name ’netSelect1
    ?buttonText "Select"
    ?callback "asiSelectNet(’net1 ?prompt \"Select net1\")"
)

 

what's the problem, tell me please!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Usually forms which use asiSelectNet will have been created as part of an ADE integration, and so will use the appropriate functions to set up the form appropriately.

    However, for a form, abVDCform in the example below, you can add a property on the form to tell it the asi session:

         abVDCform->asiSession=asiGetCurrentSession()

    or however you're getting the session (maybe sevEnvironment(sevSession) - do whatever works for your customization).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • imagesensor123
    imagesensor123 over 13 years ago

    Hi Andrew,

       sorry, i can't understand your solution very well. "abVDCform->asiSession=asiGetCurrentSession() " , what do you mean by the "abVDCform", is it a common form created by the function"hiCreateAppForm()", how to add the asiSession property to a given form? if this is ok, and then how to use the asiSelectNet(), it will work like the example showing in the user guide. i am a new guy about the ADE customization. thanks for your explaination.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    My example is not quite as you'd want it - but here it is:

    procedure(abPlotVDC()

        unless(boundp('abVDCform)
        hiCreateAppForm(
            ?name 'abVDCform
            ?fields
            list(
                list(
                hiCreateStringField(
                    ?name 'net
                    ?value ""
                    ?prompt "Net"
                )
                0:0 400:30 100
                )
            )
            ?callback 'abPlotVDCCB
            )
        )

        abVDCform->asiSession=asiGetCurrentSession()

        asiSelectNet('net ?form abVDCform)
    )

    In my case, I don't actually want the form to appear - so I'm creating the form to keep everything happy - but the idea is that whatever variable you are using to store your form in needs a property called asiSession storing the asi session id. When asiSelectNet is called, it will either use the specified form, or the current form (I think) to identify the "asiSession".

    So you need to add a property called asiSession to your form.

    I'm a bit rushed to put together a more complete example. There's one in solution 11256686 though.

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • imagesensor123
    imagesensor123 over 13 years ago

    Hi Andrew,

        yes, i think that the asiSelectNet function needs a form which contains the "asiSession" information,  so that it can know where to find object(associated objects), here, it's a net, as you said, this function is properly added in the ADE, so there should be a property storing the asiSession, i got it. thanks

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information