Hi,
Can anyone help with this issue?, I have been adding a TableLayoutPanel to a ControlContainerTool at runtime and having the TableLayoutPanel set to AutoSize = true causes the TableLayoutPanel to show outside the ControlContainerTool and the RibbonGroup it is in..and its not just that, if i set the RibbonGroup.Settings.CanCollapse = false the TableLayoutPanel dosent look like it is in the RibbonGroup when resizing the form..i have placed pictures for you to see what I am talking about:
You can see on the right that the TableLayoutPanel overlaps the button and
below you can see that on AutoSize = true for the TableLayoutPanel it draws outside the ControlContainerTool and/or RibbonGroup ..
Can anyone help please??
The latter case seems to be a bug in the group positioning logic. I have forwarded this post to the Developer Support Manager and a DS engineer will be contacting you about this issue.
As for the first issue, it makes sense that the contained control would overlap the button, seeing as how the button is just drawn onto the dock area control which owns the contained control. Obviously, this is not desired behavior though, so this is also a bug. However, we may have to just prevent CanCollapse from being set to False on RibbonGroups owning a ControlContainerTool. But hopefully a better solution can be found.
After sending you an example of reproducing the bug months ago I had the case supposedly resolved for this bug in July, I have just downloaded the lastest infragistics controls 2010.2 and expecting the bug not to be there but it still is, why is that?
I have just updated the Infragistics libraries to the latest 2011.2 in our application and noticed that the bug reported has been fixed but now the ribbon crashes with the red cross displayed. Its throwing a ArgumentOutOfRangeException.
I have attached two zip files with exactly the same code,
1. referencing the 10.3 libraries (works).
2. referencing the 11.2 libraries (crashes).
:(
Here is the test project attached using the 11.2 libraries
Ok, I am able to see the issue now. This has recently been fixed (bug id 88900) and should be included in the latest SR of 11.2. Try upgrading to this SR to see if it fixes your issue.
Hi Mike,
Use the project that references the 11.2 libraries and resize the window to normal state, not maximized.
I was not able to reproduce this exception with the sample provided. Are there any steps I need to perform to see the problem?