I'm trying to use a web slider to allow a user to increment (or decrement) data by a percentage that is tied to the slider value.
The slider appears normally when I test from within Visual Studio (VB 2008, ASP.Net 3.5, running on Vista Business 32-bit). But when I try to run the app from a browser on another computer, the web slider either doesn't appear, or it appears in some randomly mangled fashion.
What's the trick with sliders? I already found out that they're not expected to display properly within WARP panels (too bad).
------------------------------------------------------
<asp:Panel ID="Panel4" runat="server"
BorderStyle="Ridge"
ScrollBars="Auto" HorizontalAlign="Center" BorderWidth="2">
MaxValueAsString="50" MinValueAsString="-50" ToolTip="Revenues"
ValueLabel-Location="LeftOrTop" BorderStyle="NotSet" Tickmarks-Location="BottomOrRight" Visible="True">
<ValueLabel Location="LeftOrTop" /></cc1:WebSlider>
</asp:Panel>
Hello,
WebSlider is built of Aikido framework, which itself is built to work with the Microsoft ASP.NET AJAX Extensions toolset. WebAsyncRefreshPanel uses a totally different kind of AJAX functionality, which isn't compabile with the AJAX functionailty used by the ASP.NET AJAX Extensions toolset.My suggestion is to use an UpdatePanel instead of WARP.
Thanks.
I've tried the UpdatePanel from MS, and I've also tried it without any panel or tab of any kind (no WARP, no WebTab, no MS UpdatePanel, just by itself within a div). Unfortunately, I get the weird behavior in any case. I've put an issue in for Infragistics on this, but in the meantime I'm willing to try any other suggestions from this forum.
Hi Paul,
I assume that your project has local ig_res directory accessible by slider to get its css classes at run time.
It is possible that in some specific layouts and in some browsers, slider can have problems with rendering. If that is the case, then try to experiment with layout of your page and container elements of slider. I suggest you to build a temporary page, drop slider and test it. If it works correctly, then increase complexity of that page step by step to make it closer to your application. Also slider uses html elements with position:relative/absolute, it means that if page has overlapping or partially hidden html elements, then the parent of slider also should have position:relative. The worst case is IE, because div-parent with flow/default postion is not able to support children with position:relative.
If slider or its parents use % width/height, then try px values.