I am facing XamRibbonWindow title bar overlap issue when I am launching my WPF application via Win Form.
I am using "Office2k7Black" theme in the ribbon. Sample project attached with the ticket.
I need fix of this problem in WPF code with Office2k7Black theme.
This issue is reproducible in with Office2k7Black theme. This functionality is working with "Office2010" theme.
Environment : Windows 10
Technology: Winforms & WPF
I am assisting you with XamRibbonWindow overlap the window and not able to click on min, max and close button issue through your private case ‘CAS-196672-G6G5V2’ as you provided your sample code in that.
Please let me know if I may be of further assistance or if this case may be closed.
Hi Divya - As I said previously that I am not able to click on windows 'Min, Max & Close' button just because of your Infragistics Office2k7Black theme. I need all these button clickable in the sample project with the same theme.
Please fix this issue in WPF sample project only not in Win forms.
I tried to implement your suggestion in my sample code but it’s still not working.
Can you please implement those changes in the sample project (attached with ticket# CAS-196672-G6G5V2) and send back to me?
Hello Anoop ,
Thank you for the update.
As you are having initial issues implementing the work around into your internal code, I have requested to provide you the private/bi-weekly builds in order to fix the issue ASAP. I’ll keep you updating with our progress.
Also as the case has created as a trial customer I would like to know which version of control you are using (V18.1 or V17.2) to provide you the builds ?
I would also recommend you to register your product key with the account in order to not showing you as a trial customer.
I am using Infragistics V16.1 for WPF. Please provide the Infragistics patch on this version.
The comments that Divya provided are related to how the developer fixed development issue 254850 in our code. This is a change in our assemblies and to get the fix you will need to upgrade the assemblies.
Per our product lifeclycle we provide service releases for one year from the release of any volume which means that only 2017 Volume 2 and 2018 Volume 1 are currently maintained and receiving service releases. As such it will be necessary for you to upgrade you application to one of these volumes to get the fix.
Please note that even if we did still provide service releases for 2016 Volume 1, upgrading to a new service release requires that you test your entire application just like if you upgrade to a new volume release. The recommendation is that you upgrade to 2018 Volume 1 as that will be maintained and supported the longest.