I have webforms that serve multiple functions. I have a WebSplitter splitting the screen vertically, with criteria selection on the left, and the report or content on the right.
Sometimes, the criteria is provided by a querystring. In these instances, I want to completely hide the criteria pane, and I don't want the splitter bar to be visible. I just want the content to be visible.
Is there an easy way to do this?
Hello Rob,
You can use the approach shared by Viktor in the below forum thread.
The provided solution is using the ThicknessCssClass of the SplitterBar
http://community.infragistics.com/forums/p/6012/27416.aspx
Another possible solution it to collapse the "Criteria" Pane and set invisible style of the SplitterBar
.invisible
{
visibility: hidden;
display: none;
}
if (criteria){
// Collapse the criteria pane
WebSplitter1.Panes[0].Collapsed = true;
WebSplitter1.Panes[1].ScrollBars = Infragistics.Web.UI.ContentOverflow.Hidden;
WebSplitter1.Panes[1].EnableRelativeLayout = false;
WebSplitter1.BorderColor = Color.Transparent;
WebSplitter1.BorderStyle = BorderStyle.None;
WebSplitter1.BorderWidth = new Unit(0, UnitType.Pixel);
WebSplitter1.SplitterBar.CssClass = "invisible";
Let me know if you need further assistance.
Thank you very much!
Unfortunately, I am having to go through and remove most of my WebSplitters because of the bugs introduced in the new build. It is causing me an enormous amount of work. If there is anything you can do to help me with a workaround on those bugs, I would be immensely grateful.
Thank you for reporting this.
We will pay attention and will get back to you.
Also, since the WebSplitter and WebTab both use a ContentPane template, I wouldn't be surprised if the same issues are present in controls hosted in a WebTab.
I just haven't run across any or had time to build a test.
Sure, I have made two forum posts, and have submitted a support ticket for each.
Between these two issues, the WebDataTree issue is the most important. But because both are related to the WebSplitter, I wouldn't be surprised if the same fix corrects both issues.
Hi Rob,
Can you please share the issues that you experience in the new build ( I guess you mean 2064 of v11.1) ?
Hope hearing from you.