Hi,
I am using v9.2. This behaviour can be easily recreated on a new solution by creating a usercontrol (with only a textbox in it is fine). Then drag one instance of the user control on a new form. Add also a toolbarsmanager, enable the ribbon, add a tab and a group, and add a control container for the user control.
Run the solution. You can type data in the textbox. Minimize the Ribbon (double click on tab item). Now click once ONCE on the tab item (tad drops down). Try to type data in. Does not work. Click on the textbox to highlight text and try to type data in. Does not work either.
This seems to only happen with ControlContainers. Is there any property I can use to avoid this behaviour?
Thanks
Javier
Hello Javier,
The issue you describe was resolved in NetAdvantage 2010 Volume 1. If you upgrade to that version, you will no longer have this issue. Let me know if you have any other questions.
Sincerely,
Upgrading to a new version is not straightforward for us as we have different development teams that need be synchronised in order to migrate all their applications. We do not want to go through all this process for one issue, however we will not be able to use the ribbon unless this is fixed.
Is there a different option other than upgrading to 10.1 at this point? A quick workaround in code would be ideal but if not a patch release for 9.2 would also be easier to deploy in our infrastructure as we can just redirect our assembly loading to the patched version without rebuilding all applications - which we cannot do with the new release as there are breaking changes.
Thanks, Javier
Are you using the latest service release for 9.2? According to my research, this issue was fixed in the latest service release for 9.2.
Hi Dave,
We are using 9.2.20092.1003. I can see that service release 2042 was released on Dec 2009:
http://blogs.infragistics.com/blogs/vince_mcdonald/archive/2009/12/02/service-release-published-netadvantage-for-net-windows-forms-and-asp-net-december-1-2009.aspx
But according to the service releases page, latest release was scheduled for the end of April
http://www.infragistics.com/support/service-releases.aspx#ServiceReleases
Which of these two service releases has this bug been fixed in?
I managed to check against 9.2.20092.2058 and verified it was fixed there.