So the easiest thing I think is to:
group the sub menus together
group the days together
Then have them off scene at the start.
When the menu button is clicked. Have the sub menus move on scene in as short as period as possible to the correct position and then fad in.
When the classes is clicked have the days move on to scene in the same way as the sub menus do.
Now the trick bits.
When a day is clicked, it will continue the (symbol) timeline as normal, allowing the fade out. But it will hit at 00:01:15 a timeline action to ‘Go to time in timeline’ -> 00:01:15. Which is where the sub menu and days groups are off scene.
Now you will have no days or sub menus in a position to be clicked.
When the (x) button is clicked it will run the same Custom Behaviour.
The Custom Behaviour now has two actions.
Go to time in timeline :-> 00:04:27 and then Continue main timeline.
When it continues it will hit a new timeline action at the 00:05:00 mark.
This action will :
Go to time in timeline :-> 00:04.11 and then Continue main timeline - reveres.
This will act like a back button. This will reload the days and submenus.
Kirsty New tablet 3.hypetemplate.zip (1.1 MB)
So you now have a couple of tricks up your sleeve here.
Off scene movement.
Using the timeline actions with element actions to skip over timeline pauses and the actions.
Using Custom behaviours to access a symbols timeline.
The most important thing is to make life easier walk though how you want a menu system to work and how you think a user would expect it to work, If you then know you need to have it work a certain way research how before you put down too much into the project.
Otherwise it will become hard trying to fix it.