Nested MSO, slideshow inside MSO triggered by button, invisible on start, able to open/close

Question

Consider the following scenario:
(albeit, this may not even be the right way to do this, or perhaps such functionality is not possible based on existing tools at this time, however, I thought I would post and see if anyone has a trick to share...)
I have a slideshow on the page, it is set to auto play.
I would like to hide it initially, and have it trigger with a button... and then let the user close it. Much like the "light box" effects we have all come to know from the web.
Seems easy enough.
However, in my first attempt to do this I did the following:
1- create an OPEN button (F1)
2- create a container box and a CLOSE button, grpup them (F2)
3- turn them both into an MSO (M1)
4- set the button in F1 to trigger F2 (open state)
5- set the button in F2 to trigger F1 (close state)
-> test, works.
next step, slideshow!
I grab 5 images, create a new MSO (M2).
Turn it into a slideshow Folio Overlay...
-> test, works.
Now this is where it gets funky...
MY FAIL 1- If I try to take M2 and then right click M1, there is NO paste into option.
MY FAIL 2- If I click on the Object States Panel, and then Right click State 2 for M1, there is no "past into option"
MY FAIL 3- If I try to "Alt+Ctrl+V" with M2 into State 2 for M1 it does not work.
--> nor does any other scenario where I attempt to paste any MSO into another MSO
I have even tried
x- grouping the MSO slideshow with a non MSO element such as a frame, text boxt, image, ect..
x- taking the 5 images and pasting them into the MSO seperate, and then trying to turn them into a new MSO inside State 2, which the new MSO button is greyed out and will not let me apply it.
Possible solution I have come up with after looking over alot of Bob's stuff in the tutorials area
(PS his videos and tut's realy help, its a differant kind of thinking going on here with DPS, I imagine it relates to how the C in the binary works and is translated by the InDesign GUI into app code... would be nice to just type in "function on_tap(){open_slideshow(vars);}"  lol silly programmer, this is primarily a tool for designers  ... but I do think its awesomeness, as a programmer, I dont even want to write code anymore after using DPS and Phone Gap...),
so... here it is, not necessarily the most attractive...
1- Make the slide show MSO, push to BACK, set to auto play and swipe allowed...
2- place a large opaque box on top of the slideshow, group it with the OPEN button
3- create a close button
4- turn them into an MSO, now there is an 'open' button in state 1 on top of an opaque box that sends to state 2, and a 'close' button in state 2 that sends to state 1
This seems to work, I have not tested it on all devices, the iPad will kind of do this wierd glitchy thing, as if it "knows" there is something moving underneath the opaque box. Depending on how I have positioned scrollable frames on top of these elements from a stacking perspective there can be some unexpected behavior. The best results I have had from more complex layouts is to get creative with positioning...
any other suggestions, tips, tricks, would be appreciated
ON a site note:
POSSIBLE BUG:
ANYTIME I try to take ANYTHING that is already using the FOLIO OVERLAY and right click the STATE in the STATES PANEL
In Design total crash!!! The only time I can take a  FOLIO OVERLAY (FO) and "right click paste into" an MSO state is by clicking on the state on the stage, it can not be done from the panel, the panel only works with non "FO" items... Even though the state in the panel shows the "past into" option, if I do, *poof* instant app crash... FYI for anyone toying with this. Kudo's to Adobe for the outstanding "auto save" feature. It has saved me time, and there for in some strange way, has also saved some of my life.
Here is what InDesign poops out when a "Folio object" is attempted to be "pasted into" an MSO via the MSO panel.
Problem signature:
  Problem Event Name:          BEX
  Application Name:          InDesign.exe
  Application Version:          8.0.0.370
  Application Timestamp:          4f72c3ee
  Fault Module Name:          StackHash_0a9e
  Fault Module Version:          0.0.0.0
  Fault Module Timestamp:          00000000
  Exception Offset:          00000023
  Exception Code:          c0000005
  Exception Data:          00000008
  OS Version:          6.1.7601.2.1.0.768.3
  Locale ID:          1033
  Additional Information 1:          0a9e
  Additional Information 2:          0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:          0a9e
  Additional Information 4:          0a9e372d3b4ad19135b953a78882e789

Answer 1

@zagarskas – nested MSOs are currently NOT supported by Adobe.
However we could build such a construct by using ExtendScript (Adobe's flavor of JavaScript).
The problem with that is, that Buttons inside  a nested MSO will not work as expected. At least my testing is showing that.
If you want nested MSOs without Buttons (inside the nested one) or if you like to experiment, see the following thread:
http://forums.adobe.com/message/4573924#4573924
But please, read the whole thread from a to z ;-)
Uwe