As pointed out by others, you’re doing a redirect to another page after setting the menu to visible. This will revert the menu’s Visible property to its original state. So if you set its Visible to false in the markup, it will remain invisible. The workflow
is:
Calendar1_SelectionChanged1 is invoked
You set menu’s Visible to true
You do a redirect
The markup of your master page is parsed
In the markup, you set menu’s Visible to false
In the end, the menu is invisible.
I would like to suggest you to put the code setting menu’s Visible in OnLoad on the second page instead of the SelectionChanged event handler. That essentially adds another step to the above workflow:
In OnLoad of the second page, you set the menu’s Visible to true
Best Regards,
Ming Xu.
Please mark the replies as answers if they help or unmark if not.
Feedback to us
Ming Xu - MS...
All-Star
25269 Points
2235 Posts
Microsoft
Re: Masterpage to Default
May 02, 2012 08:46 AM|LINK
Hi,
As pointed out by others, you’re doing a redirect to another page after setting the menu to visible. This will revert the menu’s Visible property to its original state. So if you set its Visible to false in the markup, it will remain invisible. The workflow is:
Calendar1_SelectionChanged1 is invoked
You set menu’s Visible to true
You do a redirect
The markup of your master page is parsed
In the markup, you set menu’s Visible to false
In the end, the menu is invisible.
I would like to suggest you to put the code setting menu’s Visible in OnLoad on the second page instead of the SelectionChanged event handler. That essentially adds another step to the above workflow:
In OnLoad of the second page, you set the menu’s Visible to true
Best Regards,
Ming Xu.
Feedback to us
Develop and promote your apps in Windows Store