Tweet
Howdy,
I'm pretty sure the answer will be no on this, but I'm trying to get over the problem of closing one window only to have all windows that were opened from there, remain active.
Now I know this can be overcome if say you assign the skin to a UserDefined #, that way when you close the skin, all windows also close.
But if those windows are in the AMP section, is there anyway to allow the SHOW POSITION to accept skin names, other than being locked to Primary Window (which is <IsAmpWindow>) ?
For example.
On <isampwindow> there is a button which opens another window called USER-Test1. Now on USER-Test1 there is a button which opens another window called USER-Test2.
All windows are locked to Primary Window. Now the problem comes up, is if you close USER-Test1 (from the button on <isampwindow., it does indeed close, * BUT * USER-Test2 remains open, and now there's no way to close it unless you reopen USER-Test1 to click on the relevant button.
It would be awesome if there was an option to allow for skin names to be entered in the SHOW POSITION that way windows will remain with their parents, rather than forcing them to remain with grand(+)parents.
Just a thought. Probably my fault for trying to nest multiple windows
.
In the Metalastic skin, I got over this really easily by not using Toggle buttons, so using a Clear and Set button prevented users from closing that window when I didn't want them to, but for the skin I'm working on at the moment, I can't adopt that approach.
Any thoughts?
I'm pretty sure the answer will be no on this, but I'm trying to get over the problem of closing one window only to have all windows that were opened from there, remain active.
Now I know this can be overcome if say you assign the skin to a UserDefined #, that way when you close the skin, all windows also close.
But if those windows are in the AMP section, is there anyway to allow the SHOW POSITION to accept skin names, other than being locked to Primary Window (which is <IsAmpWindow>) ?
For example.
On <isampwindow> there is a button which opens another window called USER-Test1. Now on USER-Test1 there is a button which opens another window called USER-Test2.
All windows are locked to Primary Window. Now the problem comes up, is if you close USER-Test1 (from the button on <isampwindow., it does indeed close, * BUT * USER-Test2 remains open, and now there's no way to close it unless you reopen USER-Test1 to click on the relevant button.
It would be awesome if there was an option to allow for skin names to be entered in the SHOW POSITION that way windows will remain with their parents, rather than forcing them to remain with grand(+)parents.
Just a thought. Probably my fault for trying to nest multiple windows
.In the Metalastic skin, I got over this really easily by not using Toggle buttons, so using a Clear and Set button prevented users from closing that window when I didn't want them to, but for the skin I'm working on at the moment, I can't adopt that approach.
Any thoughts?
you might be amazed at some changes you could make :confused:
Comment