Quick Access Toolbar IsChecked never correctly set about fluent.ribbon

[batzen]

Maybe it's caused by AutomaticStateManagement. Try to disable it and see if it works. It might be caused by Blend.

[casserlyprogramming]

Sorry for the noob question, but how does one disable AutomaticStateManagement?

[batzen]

That's no noob question ;-).
The ribbon has a property AutomaticStateManagement, just set it to false.

[casserlyprogramming]

Ok. Thanks. I will have a look at this latter when I get back to my normal PC and I will let you know how I get on. Thanks for your help though batzen.

[casserlyprogramming]

Worked like a charm. May be a case for having this default to False rather than True. I leave it with you!.

[batzen]

Why close this?
It seems that we are handling state management while one is using blend, which is wrong.
Did you just use the code you posted above or is there anything else in your project that might cause this behavior? Maybe you could add a repro, tell me which version of blend you are using or if this also happens in the visual studio designer and I will see if I can find and fix the bug.

[casserlyprogramming]

Sorry, you make a valid point. It seems to work fine in Visual Studio (true/false), however, in Blend for Visual Studio 2012 it doesn't work unless AutomaticStateManagement set to False.

[casserlyprogramming]

Apart from setting a few buttons in the Ribbon itself there is nothing else in the project yet. I am just using it from scratch and will put in the rest when I get chance at another time so it really is basic at the moment. I can give you the .xaml file if you want. Is there anyway I could attach the xaml file or send it to you so you can see? I personally don't think it will change anything.

[batzen]

Then I will try to figure out why this happens. I guess we don't detect design time properly when blend is used.

[batzen]

I guessed correctly. We don't prevent state load and save while in design mode. Will fix this.

[batzen]

Should be fixed. Could you verify that please?

[casserlyprogramming]

Just a quick question. Has the RibbonWindow been removed from the assembly as I am getting the error that the tab RibbonWindow does not exist in XML Namespace.

[batzen]

I did not remove that one. But I noticed that the introduction of CalculatedHeight caused the designer to fail to render properly. Fixed that issue a few seconds ago.