Hi, this bug happened all of a sudden, I usually have the panels collapsed, so I closed our application then I opened it, and the panels didn't fly out anymore. We're serializing the last state of the layout using the method:
dockManager.SaveLayout(stream);
Which usually works fine, only this time the flyoutExtent property got set to 0 somehow. In our app we don't have any option to do this manually, so I don't have any clue on how this could've happened. We have 3 content panes, I usually use 2 of them collapsed, these 2 are the ones that don't work, the other one is fine.
Let me know what you think could've happened.
Thanks.
When I say collapsed I mean I set the auto hide on, so it collapses to the side and when I click on it, it comes out. Unfortunately I lost the bad file while updating from our source control software, but here's a video where you can see the layout of the panels in our application. The 2 panels on the left are the ones where I've seen this bug happen, it has never happened with the one on the right:
http://www.screencast.com/users/CarloToribio/folders/Jing/media/af6be012-2586-4a52-b885-3e9d2a801a0c
I attached a regular layout file so you can see what it looks like. I manually set the flyoutExtent of the collection panel pane to 0, this makes it behave the way I've described:
<contentPane name="collectionPanelPane" location="Unpinned" lastDockableState="Docked" lastActivatedTime="2010-01-29T15:41:49.4478377Z" unpinnedOrder="0" flyoutExtent="0" />
Let me know if you need more info.
When you say you make them collapsed, do you mean that you unpin them or that you are setting their Visibility to Collapsed? Can you at least provide the layout file so I can see the output? Also if you could provide some info as to what is in each of the panes in the layout, the timing with which you saved the layout (i.e. what event you used), etc.
Unfortunately I don't know how to replicate either, and it actually just happened again. I just make the panels collapsed and at some point, I can't expand them anymore.
The various means of support are described on the support page here.
With regards to your question I have never seen that come up and cannot think of a reason why it may have happened. The flyoutextent is based on the size of the pane at the time at which it is unpinned so perhaps the ActualWidth was 0. Unfortunately I cannot say what is happening and I can't seem to be able to reproduce the issue. Do you have a way to reproduce the issue where 0 gets stored?
Bump. Is this the official support place to ask about bugs?