By default Close Window will traverse up the model hierarchy, and close the first Dialog/Popup/Pop-in ancestor it finds.
You can override this default by specifying a different ancestor (higher up in the hierarchy) passing a reference to it to the optional <Dialog> trigger (which can be added by right-click > Add Element on the Close Window model).
Here's a practical example:Assume your application contains a view V, with a button opening pop-in P, which in turn contains a button opening dialog D.D contains button B which contains a Close Window element.Clicking B will close D, returning you to P.However, if the Close Window in B has a <Dialog> trigger which receives a reference to P (the reference is usually retrieved using the ancestor reference feature), then P will be closed (which implicitly means anything in it, including D, will be removed from view), returning you to V.
I hope this is not too confusing, especially if you're just starting to acquaint yourself with Tersus...
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign