I'm trying to use ATLAS to populate an Infragistics WebPanel when a user clicks the expand icon in a web browser.

However, the app fails with a javascript error of  "object required"; when I try to debug the javascript the debugger reports that "there is no source code available for the current location".

I get exactly the same problem with the infragistics UltraWebListBar.

Both Infragistics controls work fine using normal PostBacks - its only when I move the controls inside an <atlas:UpdatePanel> that I get problems.

Has anyone else had the same problem or managed to get ATLAS working with Infragistics?

hello.

if i'm not mistaken, there are several issues when using ig components inside an updatepanel. if you search this forum (and the UI forum), i think you'll find several posts about that.

1) Look in http://news.infragistics.com/ 

2) I think that only from v6.2 Infragistics controls will be compatible with ATLAS

AnatolyR:

1) Look in http://news.infragistics.com/ 

2) I think that only from v6.2 Infragistics controls will be compatible with ATLAS

i dont think so, i have tested Infra v6.2 UltraGrid with Atlas and unfortunately, it does not work properly, the UltraGrid lost it's style after postback

1) I haven't test ATLAS with v6.2(it is came out only today)

2) Infragistics people are aware problem with inline styles and as workaround suggests using external scc files and use classses instead of inline css like:

grid.DisplayLayout.RowStyleDefault.CssClass = "myRowClass";

 

AnatolyR:

1) Look in http://news.infragistics.com/ 

2) I think that only from v6.2 Infragistics controls will be compatible with ATLAS

Here is an Infragistics blog posting claiming 6.2 will work with Atlas:

http://blogs.infragistics.com/blogs/tony_lombardo/archive/2006/05/08/174.aspx

However, in reality, I find that 6.2 doesn't work with Atlas. I tried some Infragistics controls with the Atlas April CTP and that didn't work. I've tested more against the Atlas June CTP and still have problems.

I've had problems using the WebTab, WebCombo, and WebGrid with UpdatePanel. In some cases, I've had a completely functioning page with an UpdatePanel and just adding an Infragistics control to the page (and doing nothing else) caused it to break.

I sent Infragistics test projects showing things that are broken and they filed them as bugs. I just don't know how long it will take to get the problems fixed--especially since their development team won't be able to "review and assess" the situation for a week. As we need to move forward on our project, I'm investigating a couple of options:

1) Don't use Atlas and use some of the Infragistics controls' javascript functionality to do what we need. We could end up writing a lot more javascript than we want to, though.

2) Use telerik's r.a.d. controls instead if they work properly with Atlas (as they claim to be the first control library compatible with Atlas).

You can add WebInputButton to the list of broken controls. I don't know how Infragistics claims to be Atlas compatible when every control I've tried doens't work in the most basic of situations.I too have logged several problems with them.

If anyone finds out how to make these controls work, or if Telerik's controls work, please let me know.

I have tested ATLAS with newest version of telerik controls and everything work well. Thank telerik team very much.

I dont understand why the Infragistics team can profess that Infragistics control v6.2 work well with ATLAS. The truth is that many bugs appears.

Opps, I meant WebImageButton.

chrisstead,

I have reported this issue to our development team and they are working on it.  Our goal was to be 100% Atlas compatibile for 2006 Volume 2, but unfortunately some issues were not resolved in time for the 2006 Volume 2 release date.  Any remaining Atlas compatibility issues at this point have been given the highest priority, and will be fixed ASAP.  It is important that you report any issues you might run into.  Not only does this guarantee that the issue will be put into a fix queue, but it also entails you to be notified as soon as the issue is resolved.

Thanks again for the report.  I will do everything I can to ensure this fix gets into our next hotfix currently scheduled for July 21st.

-Tony

Hi dotnetvn,

The loss of style information after a postback with the UpdatePanel appears to be a bug in the UpdatePanel itself.

To reproduce, paste the following into any aspx page.

    <div>
        <atlas:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true">
        </atlas:ScriptManager>
    <style type="text/css">
    .myclass{background-color:red;}
    </style>
    <atlas:UpdatePanel ID="up1" runat="server">
    <ContentTemplate>
    <div class="myclass">I have a red background</div>
    <asp:Button runat="server" ID="button1" Text="click me" />
    </ContentTemplate>
    </atlas:UpdatePanel>
    </div>

The WebGrid, along with all Infragisitcs WebControls put their style information into inline style tags such as seen above.  We are currently working on moving this information to the Head section of the page as this is now an available option with ASP.NET 2.0, however this isn't something that can easily be accomplished.  As such, we recommend working around this problem by setting the "CssClass" property of individual Style objects of the grid to a css class defined in a linked stylesheet. 

I hope this helps.  If you have any questions please don't hesitate to contact me, or the Infragistics Developer Support Team.

-Tony

MichaelDev,

If you have any trouble getting prompt resolutions to the bugs you have sumitted please let me know.

Thanks,
-Tony

Tony,

I have tried the workaround using the cssclass for all of the styles.  The look is now preserved after an atlas postback.  However, after the postback, clicking on any of the cells in the grid causes a javascript error.  We really need a resolution/work around to this problem quickly. 

I can post the code if  you think that would be helpful.

Please let me know what we can do to resolve this issue.

Thanks,

Chad 

Tony, two things:

1) Infragistics is getting better at being more transparent about what is going on, but you guys still need to get better. For one thing, please keep your blog up to date on the current status. When you let Microsoft know that there is a problem with ATLAS, update your blog again. Your blog is our window into the people behind the company wall. We are much happier knowing that someone who can do something knows about the problem and is working on it.

2) The built in style support of the various controls from Infragistics is really a crutch for users. We really should be moving everything to external CSS files but all of the design tools for Infragistics make it very difficult to do this. For example, the cssclass property is overridden by any properties set directly on the control. The work that is being done to move the styles into the head section seems like a waste of time to me. I think your time would be better spent giving us versions of your existing theme files that are already setup to use external CSS files. Make that the official way to setup the Infragistics controls and depreciate the direct styles.

Heh, of course I would also like to see CSS Control Adapter support for Infragistics controls, but they may be a little blue sky.

crust:

I have tried the workaround using the cssclass for all of the styles.  The look is now preserved after an atlas postback.  However, after the postback, clicking on any of the cells in the grid causes a javascript error.  We really need a resolution/work around to this problem quickly. 

Chad - If you have access to the Infragistics Beta Forums (all current subscribers do), there is an updated Javascript file posted there which I believe fixes this exact problem.  The problem was found right before release and did not make it into the 2006 voulme 2 RTM bits.  You should definitely contact our Developer Support Department to make them aware of your situation, and they will do their best to find if the problem is fixed in any pending private hotfixes. 

-Tony