AWV Window close callback behavior when closing ViVA Session

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

Hi Andrew, 

Thanks for the reply! Unfortunately I can't actually contact customer support, as the portal requires 2FA and my company hasn't provided me a key. 

I'd imagine this is a rather larger issue though, as seemingly every user using ViVA is indefinitely growing a list of windows they have no way of clearing (they also exist on the symbol space thus I'd imagine take up space)

When you say report it to customer support, you mean the Case Creation Form right? Or is there a way to do it by email.

Thanks, 
Trevor

Trevor,

The information you need is the hostid of your license server (look at $CDS_LIC_FILE, ssh onto that machine and run "lmhostid"); whoever looks after your licenses should know this. Failing that, email support@cadence.com and then we may be able to help you create your login and set up the entitlements correctly.

We don't support submitting support cases by email nowadays - using the support portal is better as it ensures that we capture all the relevant information and often gives suggestions before. submitting the case which might resolve it (not in this case though, I suspect!).

I don't think the remaining non-destroyed window handle is a big concern - I think it's just a handle that remains (if I try to display the window, it's just empty). This forces them to cleanup:

foreach(win hiGetWindowList() when(win~>wsId && !member(win awvGetWindowList()) hiCloseWindow(win)))

Andrew

Trevor,

The information you need is the hostid of your license server (look at $CDS_LIC_FILE, ssh onto that machine and run "lmhostid"); whoever looks after your licenses should know this. Failing that, email support@cadence.com and then we may be able to help you create your login and set up the entitlements correctly.

We don't support submitting support cases by email nowadays - using the support portal is better as it ensures that we capture all the relevant information and often gives suggestions before. submitting the case which might resolve it (not in this case though, I suspect!).

I don't think the remaining non-destroyed window handle is a big concern - I think it's just a handle that remains (if I try to display the window, it's just empty). This forces them to cleanup:

foreach(win hiGetWindowList() when(win~>wsId && !member(win awvGetWindowList()) hiCloseWindow(win)))

Andrew

I had a bright idea, so here's a workaround. Note that this doesn't solve the situation where the init trigger is not being called (if the window is opened via the results browser, or because the last tab was closed), but it does ensure that all the exit triggers are called when the overall ViVA window is closed:

procedure(wmAwvWindowInitHookCB(windowId)
  printf("init triggered %L\n" windowId)
  ; workaround to register a close proc
  hiRegCloseProc(windowId 'wmAwvWindowExitHookCB)
  t
)

procedure(wmAwvWindowCleanupAfter()
  ; the variable in the let is a semaphore to prevent re-triggering
  ; this function as each window is closed
  let(((wmWithinAwvWindowCleanupAfter t))
    foreach(win hiGetWindowList()
      when(win~>wsId && !member(win awvGetWindowList())
	hiCloseWindow(win)
      )
    )
  )
  t
)

procedure(wmAwvWindowExitHookCB(windowId)
  printf("exit triggered %L\n" windowId)
  ; check the semaphore and schedule the cleanup. Have to use at least
  ; a tenth of a second delay - not hiEnqueueCmd or 0 for the timer - because
  ; the awvGetWindowList() is not emptied immediately.
  unless(boundp('wmWithinAwvWindowCleanupAfter) && wmWithinAwvWindowCleanupAfter
    hiRegTimer("wmAwvWindowCleanupAfter()" 1)
  )
  t
)

awvInitWindowFunctionAdd('wmAwvWindowInitHookCB)

I did file an internal CCR for the situation that the windows are not being closed properly - CCR 3302185.