Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 1519
  • 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

Decision-making upon window's closing action

abompos

Dear all,

I have created a SKILL form using (hiCreateAppForm) and attach/display it in a window using (hiCreateWindow) and (hiDisplayWindow). It was implemented in that way mainly because of some toolbar items I need to place on the window.

What I am trying to figure out is how to properly implement the scenario of closing the window via the 'X' button. Ideally, I would like a dialog-box(Yes/No/Cancel) to pop-up and act accordingly based on user's selection. In case of a 'No/Cancel', the window should remain open (as in ADE-L, ADE-XL etc.).

I've read carefully the documentation, searched the forum threads but didn't manage to find a proper way to implement this. I also did some desperate trials using (hiRegCloseProc) even though the documentation states that it shall be used strictly for clean-up and that a C closing procedure is called before any SKILL closing procedure.

Is what i'm trying to achieve simply a dead-end?

Many thanks,

Andreas

  • Hi Andreas,

    There's no SKILL support for a SKILL pre-close-window trigger. The examples you give are achieved by a lower level application trigger which allows vetoing of the close event, and are done using the C/C++ API.

    I found some discussion of this in CCR 1643712 too, which agrees with the above.

    Maybe there could be supported added for the specific situation you describe. The concern with doing it generally is that a SKILL pre-close trigger on existing applications could leave the application in an inconsistent state if it has started to clean up having decided to proceed with the close; the close trigger should not then be allowed to contradict the application's intent to close. However, for your own window forms or own applications, it seems reasonable to me that you should be able to do as you ask. So perhaps you could contact customer support through your channel and maybe we could consider doing something for this specific scenario. 

    Regards,

    Andrew

  • in reply to Andrew Beckett

    Hello Andrew,

    Thank you for getting back to me and for providing the reasoning behind the current implementation.

    I agree that for standard applications having a SKILL pre-close window trigger might be risky. It would probably make sense though, as you say, to allow this for custom windows/apps at some point.

    I will plan to log a CCR to be considered in a future implementation.

    Best regards,

    Andreas

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.