Hello Luciano,

Thanks for the sample. I investigated it and the WebDesktop Designer problem is caused by the !important value of WindowStyle's CustomRules. You could try to change it as following:

...
<WindowStyle>
    <Active BaseStyle="Normal" BorderColor="#166AEE" Overflow="Hidden">
    </Active>
    ...
</WindowStyle>
...

May I know whether you're using Unified Theming? If so, I might have another workaround for you.

Hope this helps.

Regards,
Erwin Sanders

Hello Shailendra,

Thanks for the sample. Seems like this should be an improvement to our WebTreeView because this is the first time we have a scenario with multiple colors in a WebTreeView. I reported this to our dev team, and they delivered with a nightly built hotfix which I attached for you below. To apply it manually, please follow these steps:

1. Extract the hotfix file, for example : WebTreeViewNET2_0_1500_413.zip.
2. Copy the entire contents of \bin folder and paste it to [Installation Folder]\Intersoft Solutions\WebUI Studio for ASP.NET\WebTreeView.NET 2.0\Bin.
3. Copy the entire contents of \script folder and paste it to [Installation Folder]\Intersoft Solutions\WebUI Studio for ASP.NET\CommonLibrary\WebTreeView\V2_0_1500 folder.

Regards,
Erwin Sanders

Hello Sachin,

Here I made a sample for you in which you can add a new accordion item. If you want to add the grid inside the accordion item, I suggest that you use an IFrame for such case. Call the webform with a QueryString to show the desired grid. Hope this helps.

Best Regards,
Erwin Sanders

Hi Sachin,

It's caused by the ellipsis text from our internal styling. Oddly enough, this issue only occurs on IE 11. Currently the fastest way to fix it is to remove the right margin from the input's user agent style. Try adding this style to fix the problem.

<style>
.WC4-C > input {
    margin-right: 0;
}
</style>

Hope this helps.

Best Regards,
Erwin Sanders

Hello Shailendra,

Thank you for the report. I have investigated this and seems like this is an issue from our internal code. It's been addressed under ASPNET-379. There will soon be a hotfix provided by our dev team. Thank you for your patience. In the meantime, I'll see if there's any workaround for the moment.

Best Regards,
Erwin Sanders