04-14-2020, 10:50 AM
Dean,
I make extensive use of dynamic overlays because I think it is a great feature but I’m having a behavior that I don’t know if it is by design or a bug.
I have a template with two overlays on it. Overlay A and overlay B.
Overlay A is loaded with a template that contains a group of command buttons. Each command button loads a global variable and then does a IntfViewer::LoadAncestor(../Main, GrandParent). It works great. It calls my “Main” Template which then loads an overlay with whatever was named in the global variable. Works great. Still with relative addressing.
Overlay B is loaded with a template that has a Dynamic Overlay in it. In the Layout template for the dynamic overlay there’s just a command button. It loads a global variable and tries to do the a IntfViewer::LoadAncestor(../Main, GrandParent) but nothing happens. The command button action is executed because I have a log statement in it and it gets logged. I’ve tried GreatGrantParent and Root in addition to the GrandParent but the result is exactly the same. Nothing is loaded. If I replace the a IntfViewer::LoadAncestor(../Main, GrandParent) with a IntfViewer::LoadNewTemplate(/User/Home/Master/Main) it works but I’ve lost the relative addressing.
Is the above behavior by design or a bug?
Thanks,
Bryan
I make extensive use of dynamic overlays because I think it is a great feature but I’m having a behavior that I don’t know if it is by design or a bug.
I have a template with two overlays on it. Overlay A and overlay B.
Overlay A is loaded with a template that contains a group of command buttons. Each command button loads a global variable and then does a IntfViewer::LoadAncestor(../Main, GrandParent). It works great. It calls my “Main” Template which then loads an overlay with whatever was named in the global variable. Works great. Still with relative addressing.
Overlay B is loaded with a template that has a Dynamic Overlay in it. In the Layout template for the dynamic overlay there’s just a command button. It loads a global variable and tries to do the a IntfViewer::LoadAncestor(../Main, GrandParent) but nothing happens. The command button action is executed because I have a log statement in it and it gets logged. I’ve tried GreatGrantParent and Root in addition to the GrandParent but the result is exactly the same. Nothing is loaded. If I replace the a IntfViewer::LoadAncestor(../Main, GrandParent) with a IntfViewer::LoadNewTemplate(/User/Home/Master/Main) it works but I’ve lost the relative addressing.
Is the above behavior by design or a bug?
Thanks,
Bryan