Well you know you can traverse the xml tree so put your
1a=
2b=
3c=
in the <include> at the root of the page, and then always reference this via Parent.Parent. ... - that way you only need to define it once, makes it easier to edit it.
And the other things is you could put the actual hiding code in a button at the root and have the individual pages call it in the same ways (Parent.Parent. ... .Press=true). You'd need to pass the reference of the page to the button as well, e.g. Parent.Parent. ... .CallingPage=Parent.Name and then show/hide that page.
PS: Looking at your actual code I still don't get why you have all that scripting in their configuring the dynamic data objects? Why is that needed, why not just show/hide the entire page?
Last edited by gm9 : 01-26-2009 at 04:46 PM.
|