Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 14244
  • 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

dump all the layer from Palette Assistant window in case of no LSW layer definitions in the specified technology database

zssfred

Any ideas from skill?

  • leGetValidLayerList(techGetTechFile(geGetEditCellView()))
  • works like charm!! Thank you so much Andrew. I can use this list to l_layers of hiCreateLayerCyclicField().
    Before your idea, my thinking is to use all the layers and use a callback to check. But the challenge is how to write this callback?

    Thanks.

    Fred
  • Fred,

    You could have used leIsLayerValid to check if each layer was a valid layer purpose pair - then you could use that to filter which of the complete LPP set was valid.

    Andrew
  • Andrew,

    Yes. That is what I am thinking. But the challenge is the mechanism of callback. The official doc has so limited info about callback.


    Thanks.

    Fred

  • Fred,

    I don't think I really understand what you mean. It also depends which callback you're talking about - in what context? A callback is simply a function that gets called at a particular time - but unless I know what you're trying to do, I can't really give a more precise answer.

    Andrew.

  • Andrew,

    There is "t_callback" from "hiCreateLayerCyclicField", but don't know how it works.

    Thanks.

    Fred

  • Fred,

    The callbacks for all form fields are simply a SKILL expression that is evaluated whenever the form value changes (most of them when the focus moves away from that field). The idea is that the function you call then can react to the change the user has made to the field value, and either check the value they've specified (and do something with that) or compute the value of another field based on the current value of the field.

    So it would get called whenever you picked a different value for the layer-purpose in this field.

    I'm not sure it would be very useful to offer a complete list of layer-purposes in the choices, and then have the callback check to see if it's valid; it would probably be better just to provide the list of valid layer purposes as choices and then there's no need to check that in a callback. The use model would be a bit strange otherwise.

    Regards,

    Andrew

  • Andrew,

    Totally agree what you said. The callback way works. If a user selects a LPP, the callback will check(form->layerField->value ---> techGetLP ---> techGetLPAttr) if it is valid in technology database. If it is invalid, it just tell the user and quit. But that is not good solution. The good solution is like what you elaborated here, just give all the valid LPPs to user.

    Thanks.

    Fred

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.