Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 16330
  • 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

Proper SKILL GUI programming

LeJonT

Hi,

Where can I get to see some good, rugged example of a small GUI app written in SKILL? Or some document on a proper GUI app writing methodology? The point of interest are proper Error handling, Window management, Inter app communication etc?

With the help of skuiref manual, I'm able to get my application up and running. But, bit scared about the ruggedness!

Any help would be appreciated..

-Leo

  • Not quite sure if this is what you want, but there's this post and a comment on it here.

    In general the approach is that all forms should not rely on the return value of hiDisplayForm(), but instead use callbacks to continue operations. You can choose whether your forms use things like the ?unmapAfterCB argument together with hiSetCallbackStatus() to allow the UI to stay up (with hiHighlightField() to highlight fields that are in error), or whether the form closes and the error is reported to the user via the CIW or via a dialog box (say). That's a matter of personal preference (or laziness - it's a bit more work to ensure that your form validates its fields and highlights the fields that have erroneous values).

    Best Regards,

    Andrew.

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.