How do I prevent player inputs from cascading in code?

Having trouble limiting player inputs from cascading (not sure if there is a better way to describe this problem)

Example: Two menus. Menu A opens Menu B. When Menu B is open and player hits cancel, the input cascades and closes both Menu B and Menu A.

Example Code:

-If menu B is active and player hits cancel, close menu B and make code for menu A active

-If menu A is active and player hits cancel, close menu A

Flipping order of the code does solve the problem, but if I have blocks of code in different spreadsheets, things become complex. Tried disabling groups of code and 'on/off' variables to no avail. Wondering if you guys have a simple solution that I'm overlooking!

Have you looked into using functions? Use one function for each menu? and then call them independently.

This would be one of those places to add an "else" event..

"else" is the basic way to do it, but why not just a simple cooldown variable? Whenever you do your menu 'action' just set the cooldown variable to like 0.5 (and subtract dt from it whenever it is over 0). Then another menu option can only be called if cooldown = or less than 0.

a quick dirty example https://mega.nz/#!fZtyDb7T!Vuzkrzm7gtGA ... 2qUKzHvrw4

hope it helps