Stats

  • Locked Locked
  • Replies 7
  • Subscribers 144
  • Views 25029
  • 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

Adding elements to open form in SKILL

ToMWUT
Hello,
I’ve got a question about a form. I have a form created with hiCreateAppForm function and then it was also displayed using hiDisplayFunction.
Is there any possibility using for example a callback function of a button on this form to add something to the form for example another field, so the form would reload and the user wouldn’t feel the difference? I would like to add another element to ScrollRegion.
 
Any piece of code would be much appreciated.
 
Regards,
ToM
Parents
  • Andrew Beckett

    Farhan,

    What you should do is not execute code immediately after hiDisplayForm(), but instead specify a callback using ?callback with hiCreateAppForm. That way you can tell it a function to call when the form is OK'd or Apply'd (you can also supply a different function to call if the form is cancelled).

    Relying on the blocking behaviour of a form is not considered good practice (the forms are normally blocking unless you pass ?dontBlock t to hiCreateAppForm) - a callback is the right way to do this.

    Unfortunately my example above doesn't have a callback on the main form (it does now, because I've edited it), but you could add:

    ?callback 'oferFormExampleCB

    to the hiCreateAppForm() example. Not quite sure how that went missing, but must have been a while back because even in the original version in my version control system back in 1999 I neglected to pass ?callback. I'll fix the code above

    Andrew.

Reply
  • Andrew Beckett

    Farhan,

    What you should do is not execute code immediately after hiDisplayForm(), but instead specify a callback using ?callback with hiCreateAppForm. That way you can tell it a function to call when the form is OK'd or Apply'd (you can also supply a different function to call if the form is cancelled).

    Relying on the blocking behaviour of a form is not considered good practice (the forms are normally blocking unless you pass ?dontBlock t to hiCreateAppForm) - a callback is the right way to do this.

    Unfortunately my example above doesn't have a callback on the main form (it does now, because I've edited it), but you could add:

    ?callback 'oferFormExampleCB

    to the hiCreateAppForm() example. Not quite sure how that went missing, but must have been a while back because even in the original version in my version control system back in 1999 I neglected to pass ?callback. I'll fix the code above

    Andrew.

Children
No Data

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.