Stats

  • Replies 1
  • Subscribers 148
  • Views 44
  • Members are here 0

AWV Window close callback behavior when closing ViVA Session

TF202506034656

Good evening,

I'm attaching an init and close procedure to each individual awvWindow. In doing so, I've found what I expect to be a bug (thoughhopefully I'm just misunderstanding the behavior), and am looking for suggestions on how to work around it.

If I collect the window ids of the individual AWV windows attached to my ViVA session, and I close the viva session (main window containing all the plots)O instead of each plot window, only the first window gets destroyed, and the rest persist.

These are my two test init/exit procedures. I've tested both with and without these and the behavior remains. I'm just leaving this for a potential idea to build off of.

procedure(wmAwvWindowHookCB(w_windowID)
hiRegCloseProc(w_windowID 'wmAwvWindowExitHookCB)
t
)

procedure(wmAwvWindowExitHookCB(w_windowID)
t
)
awvInitWindowFunctionAdd('wmAwvWindowHookCB)


Steps to reproduce
wins is the list of AWV windows returned from awvGetWindowList

> wins
(window:257 window:258 window:259 window:260 window:261
window:262 window:263 window:264 window:265
)

>hiGetWindowList
window:1 .... window:257 window:258 window:259 window:260 window:261 window:262
window:263 window:264 window:265

> Close viva session via top-right X

>wins
(window(invalid):1135496992(destroyed) window:258 window:259 window:260 window:261
window:262 window:263 window:264 window:265
)

>hiGetWindowList
window:1 .... window:258 window:259 window:260 window:261 window:262
window:263 window:264 window:265

What I would expect to happen, is for windows 257 through 265 to be invalid/destroyed. In practice this causes my callback to repeatedly trigger my exit procedures on the first window, 257 and runs a bunch of warnings.

EDIT: The ViVA sesion still closes, I cannot access the awv window anymore, but they're still valid as hiRaiseWindow etc returns t, it just doesn't visually show anything.

I'm on IC23.1
Thanks, Trevor



Parents
  • Andrew Beckett

    Trevor,

    There are numerous problems with these triggers - clearly it hasn't been implemented properly after the change from AWD back in IC5141. For example:

    1. When I filed the internal CCR 3297118 for the exit trigger not working, I mentioned an observation that when you closed the last window within a session window (using the X on the tab rather than the session window), it auto-adds a new window without calling the init trigger
    2. I just observed that if I use the results browser in ViVA set to "New Window" then double-clicking or Right Mouse->New Window on the signal, that doesn't call the init trigger either
    3. As you say, if you have multiple tabs open and close the containing session window, it only calls the trigger on one of the windows

    You shouldn't really rely on keeping a list of windows and checking whether they are valid or not (but I would expect them to be properly destroyed, I agree). Something is a bit fishy here...

    I'm afraid this is unlikely to get fixed unless you report it to customer support.

    Regards,

    Andrew

Reply
  • Andrew Beckett

    Trevor,

    There are numerous problems with these triggers - clearly it hasn't been implemented properly after the change from AWD back in IC5141. For example:

    1. When I filed the internal CCR 3297118 for the exit trigger not working, I mentioned an observation that when you closed the last window within a session window (using the X on the tab rather than the session window), it auto-adds a new window without calling the init trigger
    2. I just observed that if I use the results browser in ViVA set to "New Window" then double-clicking or Right Mouse->New Window on the signal, that doesn't call the init trigger either
    3. As you say, if you have multiple tabs open and close the containing session window, it only calls the trigger on one of the windows

    You shouldn't really rely on keeping a list of windows and checking whether they are valid or not (but I would expect them to be properly destroyed, I agree). Something is a bit fishy here...

    I'm afraid this is unlikely to get fixed unless you report it to customer support.

    Regards,

    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.