Current filter:
                                You should refresh the page.
                                0
                                  • Steps to Reproduce:

                                    1) set breakpoints in the constructors of the Customer and Order classes and run the project

                                    2) objects of both classes are created, which means that data is fetched for both GridViews.

                                Sample.zip
                                0

                                Does this fix apply to WebUserControl that is located on an inactive TabPage of the ASPxPageControl? I have two different WebUserControls, each on one TabPage. I notice that every time a postback or callback is performed on one WebUserControl, The other WebUserControl gets reloaded too. This has made the performance bad.
                                Thnaks.

                                Yihuey

                                0

                                Hi Yihey,

                                The fix is applied to the WebUserControl as well. A UserControl residing on an inactive Tab should not be rendered.

                                Thanks,
                                Plato

                                0

                                When I used the default setting of the PageControl, the WebUserControl on the inactive tab is rendered also. I noticed that if I set EnableCallbacks to true, then the inactive user control is not rendered. Is this the right place set? And also, even though the inactive usercontrol will not be rendered in this case, all of the Page_load method on the usercontrols, active or inactive, got called. Is it suppose to do that? why?
                                Thanks.

                                Yihuey

                                0

                                Hi,

                                The default mode of the ASPxPageControl is Client mode. In this case all the content of the ASPxPageControl is rendered. You should activate the AutoPostBack or EnableCallBacks property.

                                Thanks,
                                Plato

                                0

                                I have a web user control which has a PageControl on it with two tabs. Each tab contains a child web user control. Each child Web User Control has a GridView. If I leave the EnableCallBack and AutoPostBack of the PageControl as false, everything works fine except both child usercontrols inside the tabs are loaded and rendered when the page is loaded. If I set the EnableCallBack to true, the GridView Edit button does not work anymore, and the ComboBoxColumn of the GridView broke too.
                                Attached is my sample application.

                                To reproduce:
                                1. Change the connection string in Global.ascx to a proper database connection string.
                                2. set PopulateData.aspx as start page and run the application to populate data.
                                3. set PersonForm.aspx as start page and run the application.
                                4. Click th "Phone" tab.
                                5. Click Edit on a data row. The dropdown for PhoneType is not working.
                                6. If you change some fields of the phone number and click update, nothing is updated.
                                7. Stop debugging. Open WebUserControl1.ascx. Change EnableCallBack of the ASPxPageControl1 from true to false.
                                8. Run the application again. No problem at all.

                                I don't want to load and render the web user controls on the inactive Tabs, because it cost a lot of time. Please show me how do I accomplish this task with newly revised ASPxPageControl. Thanks.

                                NewButtonSample.zip
                                0

                                Hi,

                                We have researched the problem - the fix was not included in the 7.2.5 update by accident. In the current interim build, both UserControls are loaded (it is impossible to avoid this) but only the one positioned on the active TabPage is rendered. The bug you have described has also been fixed.

                                If you wish to obtain this issue fix, please drop us a line to support@devexpress.com.

                                Thanks,
                                Plato

                                You must  log in  or  register  to leave an answer

                                Is your intention to post an answer to your own question?

                                • If so, then proceed.
                                • If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
                                • If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.