I have a popover portal that displays a virtual list. My client would like to have two or more windows open at the same time. (ugh, i know).

Currently, if the user has two windows each with a popover portal displayed, they are parsing the same $$vlist, and so one popover's portal is showing the wrong data.

My options seem to be:

• find a way to make the $$vlist window specific
• find a way to close the first popover if the user makes a different window active (both popovers do not need to be visible at the same time)
• hide one popover by storing a key in the virtual list that compares the record to this key in the $$vlist, and if the key isn't there, the portal hides. (don't like this UX).

Thoughts? Is there a switched window trigger??

You could use named buckets for the $$var repeats:

 

$$var[ code(get(windowname)) ]

 

I've done that for all the other $$vars, Wim. Exactly what you have there (although I put Code(get(window name)) in a CF to save typing.

Hmm...why did I think that my virtual list wouldn't work this way? 

Wim! Thank you. Works perfectly.

Any suggestions as to how I can cleanup all the $$vars? I'm using them for $$active.button[wincode] in button bars, too. I suppose I can use custom menus mapped to Close and there run a cleanup script.